IBM Tivoli Storage Manager for Enterprise Resource

Planning
Version 6.4.2

Messages


IBM Tivoli Storage Manager for Enterprise Resource
Planning
Version 6.4.2

Messages


 Note:
Before using this information and the product it supports, read the information in “Notices” on page 77.

Second edition (2014)

This edition applies to version 6, release 4, modification 2 of the IBM Tivoli Storage Manager for Enterprise
Resource Planning (product number 5608-E05), available as a licensed program. It also applies to all subsequent
releases and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 1993, 2014.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this publication . . . . . . . . v Glossary . . . . . . . . . . . . . . 81
Who should read this publication . . . . . . . v A. . . . . . . . . . . . . . . . . . 81
Publications . . . . . . . . . . . . . . v B. . . . . . . . . . . . . . . . . . 83
C. . . . . . . . . . . . . . . . . . 84
Chapter 1. Introduction to Tivoli Storage D. . . . . . . . . . . . . . . . . . 85
Manager for Enterprise Resource E. . . . . . . . . . . . . . . . . . 87
F. . . . . . . . . . . . . . . . . . 88
Planning messages . . . . . . . . . . 1 G. . . . . . . . . . . . . . . . . . 88
Format of Tivoli Storage Manager for ERP messages 1 H. . . . . . . . . . . . . . . . . . 89
I . . . . . . . . . . . . . . . . . . 90
Chapter 2. Tivoli Storage Manager for J . . . . . . . . . . . . . . . . . . 90
ERP messages . . . . . . . . . . . . 3 K. . . . . . . . . . . . . . . . . . 90
L. . . . . . . . . . . . . . . . . . 91
Appendix A. Tivoli support information 69 M . . . . . . . . . . . . . . . . . 92
Communities and other learning resources . . . . 69 N. . . . . . . . . . . . . . . . . . 93
Searching knowledge bases . . . . . . . . . 71 O. . . . . . . . . . . . . . . . . . 94
Searching the Internet . . . . . . . . . . 71 P. . . . . . . . . . . . . . . . . . 94
Using IBM Support Assistant . . . . . . . 71 Q. . . . . . . . . . . . . . . . . . 95
Finding product fixes . . . . . . . . . . 72 R. . . . . . . . . . . . . . . . . . 96
Receiving notification of product fixes . . . . 72 S. . . . . . . . . . . . . . . . . . 97
Contacting IBM Software Support . . . . . . . 72 T . . . . . . . . . . . . . . . . . 100
Setting up and managing support contracts. . . 73 U . . . . . . . . . . . . . . . . . 100
Determining the business impact . . . . . . 73 V . . . . . . . . . . . . . . . . . 101
Describing the problem and gathering W . . . . . . . . . . . . . . . . . 103
background information . . . . . . . . . 73
Submitting the problem to IBM Software Support 74

Appendix B. Accessibility features for

the Tivoli Storage Manager product
family . . . . . . . . . . . . . . . 75

Notices . . . . . . . . . . . . . . 77
Trademarks . . . . . . . . . . . . . . 79
Privacy policy considerations . . . . . . . . 79

© Copyright IBM Corp. 1993, 2014 iii

iv IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages
About this publication
IBM® Tivoli® Storage Manager for Enterprise Resource Planning is an
enterprise-wide storage management application for the network. It backs up DB2®
SAP systems, Oracle SAP systems, and SAP HANA systems to Tivoli Storage
Manager storage.

This publication contains explanations and suggested actions for messages that are
issued by IBM Tivoli Storage Manager for Enterprise Resource Planning.

Who should read this publication

The target audience for this publication is system administrators who use IBM
Tivoli Storage Manager for Enterprise Resource Planning. In this publication, it is
assumed that you have a working knowledge of Tivoli Storage Manager for
Enterprise Resource Planning.

Publications
The Tivoli Storage Manager product family includes IBM Tivoli Storage
FlashCopy® Manager, IBM Tivoli Storage Manager for Space Management, IBM
Tivoli Storage Manager for Databases, and several other storage management
products from IBM Tivoli.

For more IBM product documentation, see http://www.ibm.com/support/

knowledgecenter/.

© Copyright IBM Corp. 1993, 2014 v

vi IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages
Chapter 1. Introduction to Tivoli Storage Manager for
Enterprise Resource Planning messages
Explanations and suggested actions for messages that are issued by IBM Tivoli
Storage Manager for Enterprise Resource Planning are documented.

The format of the messages is explained.

Format of Tivoli Storage Manager for ERP messages

IBM Tivoli Storage Manager for Enterprise Resource Planning messages consist of
the following elements:
v A three-letter prefix (BKI).
v A numeric message identifier.
v A one-letter severity code, also called the message type.
v Message text that is displayed on screen and written to message logs.
v Explanation, System Action, and User Response texts. These texts elaborate on
the message text and are accessible only in documentation. Many messages do
not contain System Action text.

The image presents a typical Tivoli Storage Manager for ERP message.

The callouts on the right of the image identify each element of the message.

Message Prefix
Message Number
Message Type*

BKI 0455 E

License file file name does not exist. Message Text

Explanation: The license file agent.lic was not

found where expected. Explanation

User Response: Make sure that the agent.lic

file resides in the same directory as the User Response
init<SID>.util file.

I = Information
* E = Error
W = Warning

The severity codes give an indication of the severity of the issue that generated the
message. The severity codes and their meanings are as follows:

Code Severity Meaning

E Error An error is encountered during processing. Processing might
stop. User response might be required.
W Warning Processing continues, but problems might occur later as a result
of the warning.

© Copyright IBM Corp. 1993, 2014 1

 Code Severity Meaning
I Information Processing continues. User response is not necessary.

Message variables in the message text are in italics.

2 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

Chapter 2. Tivoli Storage Manager for ERP messages
IBM Tivoli Storage Manager for Enterprise Resource Planning V6.4.2 messages are
listed in ascending numerical order. The complete message is documented.

BKI0001E Profile not specified. BKI0008E The environment variable name is not
set correctly. The current value is "value".
Explanation: Cannot locate the profile.
Explanation: The value of the environment variable
System action:
name is wrong.
User response: Ensure that a profile is available.
System action:
(Oracle) Note that the BACKINT call must have the
following form: backint –p init<SID>.utl . User response: Set name to an appropriate value.

BKI0004E Function not defined. [ function ] BKI0009E The option 'option' must be specified
after the '–t FAKE' option. This is true
Explanation: BRTOOLS, BRBACKUP, or BRARCHIVE
for all fake relevant options.
passed an invalid argument to Data Protection for SAP.
Explanation: The attempt by the Administration
System action:
Assistant to start a backup or restore simulation failed.
User response: Ensure that you have the correct
System action: Processing ends.
version of BR*Tools installed. Valid functions are: –f
backup or –f restore or –f password or –f delete or –f User response: Contact IBM support.
inquire.
BKI0010E The option 'option' contains an invalid
BKI0005I Start of program at: time. argument
Explanation: The operation started at the time Explanation: The attempt by the Administration
denoted. Assistant to start a backup or restore simulation failed.
System action: System action: Processing ends.
User response: None. User response: Contact IBM support.

BKI0006E Type for backup not defined [ type ]. BKI0011E Semantic errors were detected in the
Please use 'file' or 'file_online'. fake definition: 'definition'
Explanation: Data Protection for SAP expects as the Explanation: The attempt by the Administration
backup type parameter only file or file_online. Assistant to start a backup or restore simulation failed.
System action: System action: Processing ends.
User response: If you start Data Protection for SAP User response: Contact IBM support.
manually to do a backup, ensure that the type option
(–t) receives the correct arguments (file or file_online).
BKI0012I command: 'command'
If your Data Protection for SAP has been invoked by
one of the SAP database utilities (for example, Explanation: A backup or restore simulation was
**BRBACKUP**), ensure that the SAP backup profile started by the Administration Assistant. The command
init<SID>.sap is customized correctly. line options are shown in the message.
System action: Processing continues.
BKI0007E Mode mode requires the environment
variable environment variables to be set. User response: None.

Explanation: Not all environment variables required

have been set. At least environment variables are missing. BKI0020I End of program at: time.

System action: Explanation: The operation ended at the time

denoted.
User response: Set the missing environment variables.
System action:

© Copyright IBM Corp. 1993, 2014 3

BKI0021I • BKI0052E

User response: None.

BKI0048E No password for node node name on
server server name given on command
BKI0021I Elapsed time: elapsed time. line.When entering passwords in batch
mode, you must supply values for all
Explanation: The time needed for the complete stanzas in the profile.
operation was elapsed time.
Explanation: The batch mode of the password
System action: function requires a data set for all Tivoli Storage
User response: None. Manager server stanzas in the profile.
System action:
BKI0023I Time: current time Done: saved bytes User response: Check the profile for active server
(percent) of bytes. Estimated end time: end stanzas. Use that information and try it again.
time.
Explanation: Finished saving a specific object at BKI0049I Enter the password for node node name
current time. The saved bytes amount of the total number on server server name:
of bytes have been saved. percent shows the percentage.
This call will be completed at the estimated end time. Explanation: The password for the node node name on
the Tivoli Storage Manager server server name has to be
System action: entered for storing it in the DP for SAP configuration
User response: None. file.
System action:
BKI0024I Return code is: return code. User response: Enter the password for the
Explanation: Finished saving a specific object at corresponding Tivoli Storage Manager server.
current_time. The saved_bytes amount of the total
number of bytes have been saved. percent shows the BKI0050I Enter password for node node name on
percentage. This call will be completed at the estimated server server name again:
end_time.
Explanation: In order to avoid typing errors, you have
System action: to enter the password twice.
User response: For return codes other than 0, check System action:
the run log for warnings or error messages.
User response: Enter the password again.
BKI0027I Time: current time Object: current number
of total number in process: file_name Size: BKI0051I Password successfully verified for node
size, MGMNT–CLASS: management class, node name on server server name.
TSM–Server: server name .
Explanation: The password for the node node name on
Explanation: Data Protection for SAP started saving the Tivoli Storage Manager server server name was
current number files at current time. The total number of changed successfully.
files to save is total number. The file file name is
System action:
currently being processed. The files are transferred to
the Tivoli Storage Manager server server name, which User response: None.
stores them in the management class management class.
System action: BKI0052E Password verification for node node name
on server server name failed.
User response: None.
Explanation: The password you entered for the node
node name on the Tivoli Storage Manager server server
BKI0032E Error opening file file name: system error
name was wrong.
description
System action:
Explanation: A system error occurred during opening
of the file file name. system error description describes the User response: Enter the password again. If this error
error in more detail. still exists, contact your Tivoli Storage Manager
administrator.
System action:
User response: Read the system error description.

4 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI0053I • BKI0062E

BKI0053I Time: current time Object: current number BKI0058I Time: current time Object: object name
of total number complete: file name with: with: size restored with description
bytes saved with description object description.
description.
Explanation: The object object name was restored
Explanation: Data Protection for SAP completed successfully.
saving current number file at current time. The total
System action:
number of files to be saved is total number. The file file
_name with the size bytes is saved with the description User response: None.
object description.
System action: BKI0059E Data Protection for SAP cannot find the
client options file.
User response: None.
Explanation: Data Protection for SAP requires a client
options file (<server>.opt) for each Tivoli Storage
BKI0054I Time: current time Object: current num of
Manager server. The client options files must reside in
total num complete: file name with: bytes
the same directory. This directory must also contain a
restored with description object
client options file 'dsm.opt'. The environment variable
description .
DSMI_CONFIG must specify this directory.
Explanation: Data Protection for SAP completed
System action:
restoring of current num file at current time. The total
number of files to be restored is total num. The file file User response: Set the environment variable
name with the size bytes is restored with the description DSMI_DIR to the Tivoli Storage Manager API
object description. installation path. Set the environment variable
DSMI_CONFIG to the path of the client options files.
System action:
User response: None.
BKI0060E The command parameter parameter is not
recognized.
BKI0055I Object object name with size saved with
Explanation: The command parameter parameter is not
description description.
recognized.
Explanation: The object object name was saved
System action:
successfully.
User response: Check the command syntax and
System action:
reenter the command.
User response: None.
BKI0061W The output file file name is not valid.
BKI0056I Object object name with size restored with
Explanation: The specified output file file name could
description description.
not be created.
Explanation: The object object name was restored
System action:
successfully.
User response: Check that file name is a valid file
System action:
name on your operating system. Also check that the
User response: None. 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
BKI0057I Time: current time Object: object name
old one.
with: size saved with description
description.
BKI0062E The input file filename is not valid.
Explanation: The object object name was saved
successfully. Explanation: Unable to read the input file file name
correctly.
System action:
System action:
User response: None.
User response: Check the path and name of the input
file and the appropriate file access permission.

Chapter 2. Tivoli Storage Manager for ERP messages 5

BKI0063E • BKI0413E

BKI0063E The UTL file file name is not valid. BKI0405I The process waited num_sec seconds for
BRBACKUP in util_file_online
Explanation: Unable to read the input file file name
communication.
correctly.
Explanation: This message indicates the total amount
System action:
of time the process waited for BRBACKUP to set a
User response: Check the path and name of the table space in "begin backup" or "end backup" mode.
profile (UTL file) and the appropriate file access The wait time given is the sum of the wait times for all
permission. table spaces participating in the backup.
System action:
BKI0064E The option 'option' is not recognized.
User response: None.
Explanation: The option is not recognized.
System action: BKI0410E Cannot open or delete switch file 'file
name'. Check permissions.
User response: Check the command syntax and
reenter the command. Explanation: If Data Protection for SAP is not installed
correctly (as the root user on UNIX or Linux or
administrator group on Windows) then Data Protection
BKI0065E The argument is missing for option for SAP is not able to open the necessary
'option'. communication file to the SAP system.
Explanation: Every option requires an argument. System action:
System action: User response: Check the file permission.
User response: Check the command syntax and
reenter the command. BKI0411E Maximum time waiting for BRBACKUP
expired.
BKI0101I Enter 'cont' to continue or 'stop' to cancel. Explanation: The SAP database utilities did not
Explanation: If Data Protection for SAP is running in respond within the expected time.
unattended mode (profile keyword BATCH), it System action:
terminates the current run if operator intervention is
required. User response: Contact your SAP administrator.
System action:
BKI0412E BRBACKUP wasn't able to switch
User response: Enter 'cont' or 'stop'. requested tablespace in BEGIN/END
BACKUP mode.
BKI0102I Your reply: 'reply'. Explanation: Data Protection for SAP could not
Explanation: The reply you made is confirmed. continue the backup, because BRBACKUP was not able
to switch the requested table space in BEGIN or END
System action: backup mode. This is necessary for locking the table
User response: None. space.
System action:
BKI0311E Request canceled by user User response: Contact your SAP administrator.
Explanation: (Oracle) BACKINT terminated at user's
request. (DB2) Program terminated at user's request. BKI0413E Error while requesting tablespace
System action: switch.

User response: None. Explanation: BRBACKUP could not switch table space
in BEGIN or END backup mode.

BKI0400I The process is waiting for BRBACKUP. System action: Contact your SAP administrator.

Explanation: The process is waiting for BRBACKUP to User response:

set a table space in the begin/end backup mode.
System action:
User response: None.

6 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI0414E • BKI1002E

User response: Make sure you have the right agent.lic

BKI0414E Error while requesting tablespace
file for the right platform installed. agent.lic files are
switch.
platform dependent.
Explanation: BRBACKUP reported an error while
trying to switch a table space in BEGIN or END
BKI0458I Fake–Mode is activated.
backup mode.
Explanation: This message signals that the current
System action:
operation is a simulated operation. Simulations can be
User response: Contact your SAP administrator. performed using the Administration Assistant.
System action:
BKI0452E This version of Data Protection for
User response: None.
SAP(R) has expired.
Explanation: This is a test version that has expired.
BKI0460E No mux file is found with the name
System action: name
User response: Order a release version of the product Explanation: A mux file is a data structure holding
or contact your IBM/Tivoli Sales Representative. internal metadata needed for restore puposes. Each
backup image gets a mux file assigned.
BKI0453W This version of Data Protection for System action:
SAP(R) will expire in number days.
User response: Check the logs for further information.
Explanation: This is a test version with a time limit. It If the problem cannot be resolved contact your IBM
will expire in number days. support personnel.
System action:
BKI0461I Created tracefile 'tracefile' for process ID
User response: Order a release version of the product
'id'.
or contact your IBM/Tivoli Sales Representative before
the version expires. Explanation: The named trace file has been created.
System action:
BKI0454I *** This copy is NOT FOR RESALE. ***
User response: None.
Explanation: This version is not for resale.
System action: BKI1000E syntax error in line line : 'statement'
User response: None. Explanation: The statement statement in the Data
Protection for SAP profile is unknown or incorrect.
BKI0455E License file file name does not exist. System action:
Explanation: The license file agent.lic was not found User response: Correct the error and try again.
where expected.
System action: BKI1001E syntax error in file 'file name'. Exiting
program.
User response: Make sure that the agent.lic file resides
in the same directory as the init<SID>.utl file. Explanation: A syntax error has been detected in the
file file name and the action has been halted.
BKI0456E Unable to access license file file name. System action:
Explanation: The license file could not be accessed. User response: Correct the error(s) in the file file name
and try again.
System action:
User response: Make sure the access permissions
BKI1002E BACKUPIDPREFIX must be
allow read/write access.
number_of_characters characters !
Explanation: The length of BACKUPIDPREFIX must
BKI0457E License file file name contains invalid
be number_of_characters characters.
data/checksum.
System action:
Explanation: The license file is invalid.
User response: Enter a BACKUPIDPREFIX with the
System action:
required length (for example, SAP___, BKI___).

Chapter 2. Tivoli Storage Manager for ERP messages 7

BKI1003W • BKI1016W

BKI1003W Please set redolog_copies to a number BKI1009W Please set MULTIPLEX to a number
between min_copies and max_copies a. between 1 and max_multiplex. Now it is
Now it is set to act_copies. set to act_multiplex.
Explanation: Data Protection for SAP currently Explanation: You have set multiplexing to an
supports 1 to 9 copies of offline (redo) log files. unsupported number. Data Protection for SAP now
uses act_multiplex.
System action:
System action:
User response: Adapt the REDOLOG_COPIES settings
in the Data Protection for SAP profile. User response: Set multiplexing to a number between
1 and max_multiplex.
BKI1004W You should specify the
BACKUPIDPREFIX before the BKI1011W The sortfilename 'sortfile_filename' should
TRACEFILE statement. So that the be absolute!
BACKUPIDPREFIX can be used in the
Explanation: None.
tracefilename.
System action:
Explanation: The BACKUPIDPREFIX is used to build
the Name of the tracefile. Therefore, User response: Specify an absolute file name, for
BACKUPIDPREFIX must be specified before the example /oracle/C21/dbs/sortfile.
TRACEFILE statement.
System action: BKI1012E Configfile not found or permission
denied: 'configuration_filename'.
User response: Define a 6–character
BACKUPIDPREFIX in the Data Protection for SAP Explanation: Data Protection for SAP is unable to read
profile (for example, SAP___, BKI___) the file configuration_filename.
System action:
BKI1006E The SERVERNAME must be less than
max_char characters. User response: This error could have various reasons,
try the following: 1. Check the path of the
Explanation: You have used a SERVERNAME with configuration file. The path must be specified in the
more than max_char characters. profile (parameter CONFIG_FILE). 2. Make sure that
the file access permissions are set correctly.
System action:
User response: Use a shorter SERVERNAME.
BKI1013E Profile not found or permission denied:
'profile_filename'.
BKI1007E The NODENAME must be less than
Explanation: Data Protection for SAP is unable to
max_char characters.
open the profile profile_filename.
Explanation: You have used a NODENAME with
System action:
more than max_char characters.
User response: (Oracle) Ensure that the SAP backup
System action:
profile init<SID>.sap contains a valid entry util_par_file
User response: Use a shorter NODENAME. for the Data Protection for SAP profile. (DB2) Ensure
that the vendor environment file contains a valid entry
XINT_PROFILE. Furthermore, this file must be readable
BKI1008E The MANAGEMENTCLASSNAME
by Data Protection for SAP.
must be less than max_char characters.
Explanation: You have used a
BKI1016W The tracefilename 'file name' could not be
MANAGEMENTCLASSNAME with more than
opened for writing!
max_char characters.
Explanation: The trace file could not be opened for
System action:
writing.
User response: Use a shorter
System action:
MANAGEMENTCLASSNAME.
User response: Ensure that you have specified a
correct path for the trace file.

8 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI1017E • BKI1202E

BKI1017E The server server is already defined. BKI1024E The file filename occurs twice in the
Please use another name or specify <infile>
TCP_ADDRESS!
Explanation: The named file name occurs multiple
Explanation: The named server was already defined times in the infile which is a violation of the interface
in the profile. Server stanzas with identical names are specification.
not allowed unless the keyword TCP_ADDRESS is
System action:
defined in one of them.
User response: Check the logs for further information.
System action:
If the problem cannot be resolved contact your IBM
User response: Update the profile accordingly and try support personnel.
again.
BKI1081E Unable to detect the database
BKI1019E Failed to respond to a message received environment.
from XINT.
Explanation: The operation requires special
Explanation: This messages indicates an internal error. environment settings, e.g. the database instance owner
environment.
System action:
System action: Processing ends.
User response: Contact IBM Support.
User response: Please run the command as database
instance owner.
BKI1021E component_name terminates the
connection due to a previous error.
BKI1158T Service service not completed
Explanation: A serious error has occurred which
caused a shutdown of the communication channel Explanation:
between the component_name process and this
System action:
application.
User response:
System action:
User response: Look for previous error messages to
BKI1201E There are no Tivoli Storage
detect the root cause of the problem.
Manager–Servers available.
Explanation: Data Protection for SAP cannot locate a
BKI1022E component_name terminates the
Tivoli Storage Manager server. This may be due to a
connection due to a previous error.
configuration problem or to a problem while trying to
Explanation: See message BKI1021E. connect to the Tivoli Storage Manager server. Most
probably, a preceding error message points to the cause
System action:
of the problem.
User response: See message BKI1021E.
System action:
User response: Look for and respond to preceding
BKI1023W Could not establish connection to log
error messages. You may also want to check the Data
server log server name.
Protection for SAP profile and the IBM Tivoli Storage
Explanation: In the Data Protection for SAP profile, Manager client options and client system options files.
log server log server name is specified (keyword
LOG_SERVER). However, a connection to the server
BKI1202E You must specify either
named could not be established. No log records are
MAX_SESSIONS, or all three specific
sent to the log server.
session options
System action: (MAX_ARCH_SESSIONS,
MAX_BACK_SESSIONS, and
User response: v Check that the server name defined MAX_RESTORE_SESSIONS).
with keyword LOG_SERVER is spelled correctly in the
Data Protection for SAP profile. v Make sure there is a Explanation: Information on the number of Tivoli
SERVER section in the profile for the log server defined Storage Manager client sessions to be established by
with keyword LOG_SERVER. v Check the Data Protection for SAP is missing from the profile.
corresponding SERVER section and correct any setup
System action:
problems. v Make sure that the log server named is
available. User response: In the Data Protection for SAP profile,
either specify a value for keyword MAX_SESSIONS, or

Chapter 2. Tivoli Storage Manager for ERP messages 9

BKI1203E • BKI1212W

specify values for the three specific session parameters

BKI1208W Retrying object: 'file name'. Retry count:
(MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS, and
[retry_num].
MAX_RESTORE_SESSIONS). Any of the specific
options can be specified in combination with Explanation: An error occurred while processing
MAX_SESSIONS. Then, it overrides the value of object file name. Data Protection for SAP is repeating the
MAX_SESSIONS for the specific function. action according to the number of retries specified in
the profile. retry_num is the current retry count.
BKI1203E Not enough sessions available (sessions System action:
required and max_sessions available).
User response: If the problem persists check for and
Explanation: The sum of available sessions specified respond to preceding error messages.
in the various server statements (parameter SESSIONS)
does not cover the required number of sessions
BKI1209E Object not found or not accessible:
(parameter MAX_SESSIONS).
'objectname'.
System action:
Explanation: The object cannot be located.
User response: Change the values of the
System action:
corresponding parameters in the Data Protection for
SAP profile, so that the condition mentioned in the User response: The backup integrity is affected.
explanation is fulfilled. Contact SAP or IBM Support.

BKI1205E If you want num_redo BKI1210E Input file not found or not accessible:
REDOLOGCOPIES you should give me 'file name'.
at least num_mc different Archive
Management Classes. Explanation: Data Protection for SAP cannot locate the
temporary file named. This file contains the list of
Explanation: Data Protection for SAP requires that the Oracle objects to be backed up or restored. It is passed
number of different Archive Management Classes to DP for SAP by one of the BR*Tools utilities.
(parameter BRARCHIVEMGTCLASS) on the Tivoli
Storage Manager servers is equal to or greater than the System action:
number of redo log or log file copies (parameter User response: Ensure that you have the correct
REDOLOG_COPIES). version of BR*Tools installed. For details, check with
System action: the release notes (RELNOTE).

User response: Define at least as many different

Archive Management Classes as log file copies BKI1211E There is something wrong with your
requested. CONFIG_FILE 'file name'.
Explanation: There is a problem with your Data
BKI1206W If you want num_redo Protection for SAP configuration file setup.
REDOLOGCOPIES you should give me System action:
at least num_mc different Archive
Management Classes. User response: Check the file permission and the file
name specified in the Data Protection for SAP profile
Explanation: The message appears during a keyword CONFIG_FILE.
BRBACKUP run. A BRARCHIVE run afterwards would
fail.
BKI1212W The file 'file name' is not found in the
System action: manual sorting file.
User response: Define at least as many different Explanation: The file you want to back up was not
Archive Management Classes as log file copies found in the manual sorting file.
requested.
System action:

BKI1207E Directory backup not supported. User response: Check and correct the manual sorting
file so that it contains all the files you are backing up.
Explanation: This option is not yet available.
System action:
User response: Wait for a future release of Data
Protection for SAP, which supports this option.

10 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI1214E • BKI1228W

BKI1214E TSM Error: error text BKI1223W A Problem occurred during send of
performance data to the Administration
Explanation: The specified TSM error occurred.
Assistant.
System action:
Explanation: There was a problem sending the
User response: Check error text and correct the performance data to the Administration Assistant over
problem. For further information you may want to the network.
refer to IBM Tivoli Storage Manager Messages,
System action:
SC32–9090.
User response: Check your setup or contact IBM
Support.
BKI1215I Average transmission rate was gb per
hour GB/h (mb per second MB/sec).
BKI1224W Unable to initialize connection to
Explanation: The average transmission rate is
Administration Assistant.
displayed.
Explanation: No operational data could be sent to the
System action:
Administration Assistant during database backup or
User response: None. restore.
System action:
BKI1216E There are no backup management
User response: Check the logs for further information
classes available.
and try again.
Explanation: The BRBACKUPMGTCLASSES you have
specified in your init<SID>.utl file are not correct.
BKI1227I Average compression factor was number.
System action:
Explanation: The data transferred had been
User response: Check the management classes on the compressed by the factor number.
TSM server and specify correct ones.
System action:
User response: None.
BKI1217E There are no archive management
classes available.
BKI1228W Server server name can not be used with
Explanation: The BRARCHIVEMGTCLASSES you
password access method GENERATE in
have specified in your init<SID>.utl file are not correct.
this environment. The process is
System action: running with user ID userid but the
effective user ID is userid effective.
User response: Check the management classes on the
TSM server and specify correct ones. Explanation: The user ID and the effective user ID of
the process are different. In order to utilize the
password access method GENERATE the IDs must be
BKI1218E Environment variable TEMP not set equal.
Explanation: The required environment setup is System action:
incomplete.
User response: Under UNIX and Linux, change the
System action: value of the "PASSWORDACCESS" parameter in file
User response: Set the environment variable TEMP dsm.sys from 'generate' to 'prompt'.. Under Windows,
and try again. change the value of the "PASSWORDACCESS"
parameter in file server name.opt from 'generate' to
'prompt'.
BKI1222E Version mismatch error. Please check
setup (version_1:version_2). Reset the node's password on the Tivoli Storage
Manager server.
Explanation: Different components with inconsistent
versions are used. In an Oracle environment, run

System action: backint -f password

User response: Check your setup or contact IBM In a DB2 environment run
Support. backom –c password
This will prompt you for the TSM password and then
will encrypt it in the Data Protection for SAP configfile.

Chapter 2. Tivoli Storage Manager for ERP messages 11

BKI1229E • BKI1509E

This step needs to be repeated each time your operation has ended and try again. Make sure that
password expires. multiple operations are not started concurrently for a
database. If this is a cooperative operation with two or
more participating partitions, check that the profile
BKI1229E Value for parameter BUFFSIZE (actual
settings of the various partitions (for example,
cur_number, maximum max_number) is
DEVICE_TYPE, MAX_VERSIONS, etc.) do not differ. If
too large for BUFFCOPY mode
they do, fix the profile settings, cancel the current
PREVENT.
operation, and start the operation again. Also,
Explanation: To utilize the BUFFCOPY mode investigate the possibility of sharing the same profile
PREVENT the value for the parameter BUFFSIZE must among all partitions.
not be larger than max_number.
System action: BKI1506E Error: 'description' on host 'hostname'
while executing command 'command'.
User response: In the Data Protection for SAP profile,
specify a BUFFSIZE less or equal to max_number if you Explanation: The system tried to execute the
need to prevent copying buffers when passing data command cited. During execution, an error occurred.
between Tivoli Storage Manager components. If you The output received from the command shell is listed
need large buffers you can set option BUFFCOPY to following the message.
SIMPLE or AUTO. As a consequence, buffers are
System action:
copied when data is passed between Tivoli Storage
Manager components. User response: Determine the cause of the problem
from the command and the output listed in the
message, and resolve the problem.
BKI1230E The following file was not processed:
path.
BKI1507E The process needs to run with root
Explanation: The operation was terminated due to a
authority.
previous error. As a consequence, the file named could
not be processed. The cause of the error should be Explanation: The current process requires root
found in an earlier message. authority.
System action: System action:
User response: Check for and respond to preceding User response: Start the process under an account
error messages. with root authority.

BKI1231E Maximum number of retries for file BKI1508E The service service_name has terminated
filename exceeded. due to a previous error. Please check all
logs for additional information.
Explanation: The number of retries configured in the
profile keyword 'FILE_RETRIES' for the named file Explanation: The cited service is no longer available.
were reached.
System action:
System action:
User response: Check the appropriate logs for the
User response: Check the logs for further information cause of its termination.
about the root cause of the retries. Resolve these issues
and perform the operation again.
BKI1509E Authentication failure. The password
specified is not authorized for accessing
BKI1505E Operation aborted because a different component. Please verify that the
operation by this database client is passwords specified in the password
already running. files on the different production and
backup/cloning systems are correct.
Explanation: Different concurrent operations of the
same type were started for the same database. This is Explanation: To access the named component, a
not supported. The current operation is aborted. This password is required. However, the password provided
message is also issued when a cooperative operation of could not be verified.
two or more participating partitions was started, but
System action:
the profile settings used for the various partitions do
not match. User response: Make sure that the password files used
by the different components of the system match.
System action:
User response: Wait until the currently running

12 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI1510I • BKI1521I

BKI1510I New connection received from host BKI1517I Deleting target data container defined
hostname. by container_description.
Explanation: The server received a new connection Explanation: The data in the container indicated is
request. removed.
System action: System action:
User response: None. User response: None.

BKI1512E An error occurred during shutdown: BKI1518E Internal error: The system is trying to
Error information use the same device agent, although the
synchronization mode is not
Explanation: During shutdown of the component, a
PARALLEL.
problem occurred. The error information is given.
Explanation: The system has been told to use the
System action:
same device agent for multiple database clients, but the
User response: Resolve the problem indicated by the database indicated serial synchronization mode. This
error information. setup is not supported.
System action:
BKI1513I *****> Database client connected:
User response: Contact your IBM support personnel.
instance instance, database
database_namepartition_numbernodename
BKI1519E A failure occurred during initialization
Explanation: This message follows a message
of one or more of the nodes
BKI1511I and indicates the connection of one of the
participating in this operation. Please
database clients taking part in the operation. A
check the logs for more information.
database client is an instance of the snapshot backup
library representing a single partition of the database. Explanation: Some problem occurred during the
initialization of a new operation. The problem may be
System action:
with any component required for this operation.
User response: None.
System action:
User response: Check the acsd log file for messages
BKI1514I *****> Device client connected.
BKI1515I to determine the log file names of the
Explanation: This message follows a message participating agents. Check the log files of each
BKI1511I and indicates the connection of one of the component for the cause of the problem.
device clients taking part in the operation. A device
client is an instance of the device agent for the storage
BKI1520E Volume volume_name is shared across
device.
partitions. Volume sharing is not
System action: allowed.

User response: None. Explanation: At least two partitions own data residing
on the volume indicated. This setup is not supported.

BKI1515I Client is logging to file_name System action:

Explanation: The client's log messages are written to User response: With the current disk layout of the
the indicated file. database, the requested function cannot be used. If you
want to use the function, change the disk layout of the
System action: database so that each data volume is dedicated to a
User response: None. partition.

BKI1516I Deleting container container. BKI1521I Retaining number backups

Explanation: Explanation: When enforcing profile parameter

MAX_VERSIONS, the indicated number of backups is
System action: kept.
User response: System action:
User response: None.

Chapter 2. Tivoli Storage Manager for ERP messages 13

BKI1522E • BKI1536E

BKI1522E The requested meta–information BKI1530E Failed to launch the device agent for
(subject="description") is not available. device_type. Please consult your user
documentation to make sure that all
Explanation: Some meta–information about each
requirements for the specified device
backup is stored in the repository. An error occurred
are met.
when trying to retrieve part of this information.
Explanation: The system was unable to launch the
System action:
appropriate device agent for the type indicated because
User response: Contact your IBM support personnel. some of its requirements are not met.
System action:
BKI1523W Warning: The following containers were
User response: Refer to your user documentation and
reused without being explicitly released:
make sure that the system is set up correctly for the
description
specified device type.
Explanation: The containers defined by the
description are used by the current backup. They were
BKI1534E Unexpected version actual_version of the
used before by a different backup. This message is
repository located at path. Expected
expected in SAN environments where data containers
version: supperted_version
are usually kept until they are reused. In this case, this
message does not indicate a problem. Explanation: The server located the repository in the
path indicated. However, the version of the repository
System action:
located on disk does not match the current version of
User response: None. the server.
System action:
BKI1525E The process service_name is in an
User response: Make sure to use the correct instance
inconsistent state. Please check for
of the server. Ensure that the path of the repository was
previous errors and restart the process
specified correctly. Refer to the release notes for a list of
afterwards.
possible incompatibilities.
Explanation: The process indicated cannot continue
with inconsistent data.
BKI1535E Unexpected characteristics
System action: (bitwidth=bitwidth repository) of the
repository located at path. Expected
User response: Check the logs for messages pointing bitwidth: bitwidth expected
to the cause of the inconsistency. After resolving any
problems, restart the process. Explanation: The repository located in the path
indicated was saved to disk using a bit width different
from the bit width the server is using to load the
BKI1526E A configuration file (profile) must be repository.
provided.
System action:
Explanation: An operation was started without
providing a profile. User response: Make sure to use the correct instance
of the server. Ensure that the path of the repository was
System action: specified correctly. Refer to the release notes for a list of
User response: Check the user documentation on how possible incompatibilities.
to provide the profile to the current process. Start the
process again using a valid configuration file. BKI1536E The repository located at path is not
valid.
BKI1529E The device 'device_type' is not supported Explanation: A repository could not be found at the
by the wizard. location indicated by path.
Explanation: The device type represents a certain type System action:
of storage device. While using the setup wizard, a
device type was entered that is not supported by the User response: Ensure that the path of the repository
current version of the wizard. was specified correctly. Do not edit any files in the
repository path.
System action:
User response: Refer to your user documentation for a
list of the device types that are supported by default.
Specify one of the supported types.

14 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI1537E • BKI1544E

BKI1537E The repository located at path was BKI1541E /etc/inittab was not updated because
written with an incompatible protocol some of the processes have apparently
(protocol_version incompatible). Expected been added. Please re–run the setup
protocol: protocol_version expected after calling the setup script with option
'–a disable' if you want to change to a
Explanation: The repository found at the location
standard setup.
indicated was written to disk using the protocol
version named. However, the server currently supports Explanation: During the automatic setup, entries for
the expected protocol version. this product were detected in /etc/inittab. This is an
indication that the product was not previously
System action:
uninstalled.
User response: Ensure that the path of the repository
System action:
was specified correctly. Do not edit any files in the
repository path. User response: Run the setup with option '–a disable'
and then start the installation process again. If the
entries in /etc/inittab should be retained, refer to your
BKI1538E Unexpected repository type. The path
user documentation for information on how to
'path' does not point to a repository of
complete the installation manually.
type "protocol_type".
Explanation: The repository located in the path
BKI1542E Failed to uninstall because some of the
indicated was written to disk using a protocol different
processes to be uninstalled are still
from the protocol supported by the server process.
listed in /etc/inittab. Please re–run the
System action: setup after stopping the component by
calling the setup script with option '–a
User response: Make sure to use the correct instance stop'.
of the server. Ensure that the path of the repository was
specified correctly. Refer to the release notes for a list of Explanation: Before uninstalling the product, the
possible incompatibilities. affected processes must be stopped. This is done by
running the setup script with the option '–a stop',
which will remove the entries from /etc/inittab and
BKI1539E Root privileges required. Could not stop the processes.
change user ID to root.
System action:
Explanation: The requested operation requires root
privileges. However, the process could not acquire User response: Refer to your user documentation for
them. information on the uninstall process. Run the setup
with the option '–a stop' and then continue
System action: uninstalling.
User response: Make sure the appropriate privileges
(s–bit) are granted to the executable. BKI1543E The component is still referenced within
the /etc/inittab. In order to terminate the
BKI1540E /etc/inittab entries are limited to 127 component re–run the setup script with
characters. Please consult your user option '–a stop'.
documentation for information on Explanation: The setup utility detected that the
manually completing the installation product is still active in the system. Apparently, its
procedure. entries in /etc/inittab are not yet removed.
Explanation: The command line generated by the System action:
setup function exceeds 127 characters. This situation
requires user intervention. The setup function did not User response: Call this process again with the option
update /etc/inittab. '–f stop'.
System action:
BKI1544E New entries cannot be added to
User response: Refer to your user documentation for /etc/inittab because it already contains
information on what entries to add to /etc/inittab. too many entries starting with 'ac'.
Please refer your user documentation for
a manual setup of this package.
Explanation: During setup, an unusually high number
of entries beginning with 'ac' were detected in
/etc/inittab. /etc/inittab was not modified.

Chapter 2. Tivoli Storage Manager for ERP messages 15

BKI1545E • BKI1556E

System action: resolved the daemon will take care of the deleted
backups eventually.
User response: Determine if these entries are
expected, or if they were added due to a problem. If
these entries are required, refer to your user BKI1549E Failed to load component_name
documentation for information on how to complete the
Explanation: The system was unable to load the
installation manually.
named component of the product.
System action:
BKI1545E oldprod is currently running.
User response: Contact IBM Support.
Explanation: This failure happens during
(de)installation and indicates that not all TSM for ACS
components could be stopped. BKI1553I Component_name is logging to path
System action: Explanation: The file denoted is the log file of the
named component.
User response: Check that no backup or restore is
currently running and retry the operation. If you have System action:
customized the process of starting TSM for ACS, it
might be necessary to manually stop it by undoing User response: If you need to check the log of the
those customization steps. indicated component, look for this message to identify
the log file to examine.

BKI1546E IBM Tivoli Storage Manager for Advanced

Copy Services was not started. BKI1554W The agent 'component_name' terminated
with exit code number.
Explanation: This failure happens during installation
and indicates that not all TSM for ACS components Explanation: The process denoted ended with the
could be started successfully. given exit code.

System action: System action:

User response: Check that all TSM for ACS User response: Check the agent's log for any messages
components have the appropriate access rights and pointing to a problem. Resolve any problem indicated.
retry the operation. Contact the support function if the
operation continues to fail. BKI1555I Profile successfully created.
Explanation: The profile wizard created a new profile.
BKI1547E Failed to remove the data associated
with the deleted backup backup_id. System action:

Explanation: The backup named was deleted. User response: The setup script recognizes
However, its data could not be removed from the components being restarted so that the new settings
repository and from the storage device. become active..

System action:
BKI1556E Some data of backup backup_id are
User response: Look for a previous message pointing unavailable. It is impossible to restore
to the cause of the problem. Resolve any problems the data requested.
indicated there. Once the cause of this problem is
resolved, the daemon will take care of the deleted Explanation: The system detected that some of the
backups eventually. data originally contained in the backup is no longer
available. The occurrence of this message depends on
the type of storage device employed. For example, if an
BKI1548E Failed to monitor the data associated earlier backup data was restored from an N–Series
with the deleted backup backup_id. device, some data of a later backup will be destroyed.
Explanation: A background daemon is supposed to System action:
monitor the states of backups in order to determine if
data needs to be deleted from the storage device. User response: The backup is no longer complete and
However, the monitor was not able to access the cannot be used for the requested operation. Try the
appropriate data. operation with a different backup.

System action:
User response: Look for a previous message pointing
to the cause of the problem. Resolve any problems
indicated there. Once the cause of this problem is

16 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI1557I • BKI1568I

System action:
BKI1557I Device client is logging to path
User response: Correct the name.
Explanation: The device agent's log messages are
written to the file named.
BKI1562E Deleting the backup as requested is
System action:
impossible while any part of it is
User response: None. mounted.
Explanation: A request was sent to delete a backup.
BKI1558E There are no mount agents registered However, some parts of the backup were still mounted.
for participant(s) participant_list Presumably, a restore operation or an off–loaded tape
backup is pending or in progress. Please note that an
Explanation: During a snapshot backup run, TSM for
offloaded tape backup requires the snapshot backups of
ACS detected that for the listed participant(s) no TSM
all partitions of the database.
for ACS device agent was started with the 'force mount'
(–F) option. Typically, a participant corresponds to a System action:
DB2 partition. The current snapshot backup run will be
User response: Wait until the operation in progress
deleted.
has ended, then issue the delete request again.
System action:
User response: Make sure that for each participant BKI1563I The snapshot backup defined by
(DB2 partition) a TSM for ACS device agent is started timestamp timestamp for instance
with the mount force option (–M) on the offload instance, database database_name, and
system. partition partition_number cannot be
restored.
BKI1559E Failed to verify consistency of Explanation: This message appears when backups are
DataContainer (data_container) queried for a restore. It indicates that a snapshot
backup was encountered that is not in a restorable
Explanation: During a snapshot backup run, TSM for
state. For example, snapshot backups created with a
ACS detected that the listed data container (typically an
FLASHCOPY_TYPE of NOCOPY are not restorable.
AIX® volume group or an N Series volume) could not
When queried for restore, unrestorable snapshot
be imported/mounted successfully on the offload
backups are not returned to the caller and therefore
system. The current snapshot backup run will be
cannot be selected for restore.
deleted.
System action:
System action:
User response: None.
User response: Check the TSM for ACS device agent
log/trace file for errors and restart the snapshot backup
after the problem is corrected. BKI1564W Backup id is marked for deletion. You
need to unmount before it can be
physically deleted.
BKI1560E Not all file systems have been validated
by the mount agents! Explanation: A snapshot backup with the named id
can only be deleted if all of its assigned file systems are
Explanation: During a snapshot backup run, TSM for
unmounted successfully.
ACS detected that not all file systems could be
mounted successfully on the offload system. The System action:
current snapshot backup run will be deleted.
User response: Issue the offload agent with the
System action: command '–f unmount'. After all resources are freed,
the deletion of the snapshot backup will be started.
User response: Check the TSM for ACS device agent
log/trace file for errors and restart the snapshot backup
after the problem is corrected. BKI1568I Removing backup backup_id from the
repository because it has not been found
on the storage device during
BKI1561E Profile name profile_name does not point
reconciliation.
to a file.
Explanation: During reconciliation the backup with id
Explanation: The profile specification should be a
backup_id has not been found on the storage device.
fully qualified filename. Otherwise, it is assumed to be
Therefore it is deleted from the repository to keep the
relative to the current directory of the command that
repository and the valid backups on the storage in
issues the message, which may not be the desired
sync.
directory.

Chapter 2. Tivoli Storage Manager for ERP messages 17

BKI1569I • BKI1582I

System action:
BKI1573I The container 'volume_name' has been
User response: None. successfully deleted from the storage
box. It didn't belong to any backup in
the repository.
BKI1569I Updating backup backup_id in the
repository because some data was not Explanation: The volume volume_name has been
found on the storage device during successfully deleted from the storage box during
reconciliation. reconciliation because it didn't belong to any backup in
the repository.
Explanation: Backup data with the identifier backup_id
is no longer available on the storage device. Depending System action:
on storage device settings, the space from older
User response: None.
backups might be reused to create new backups. This
information is updated in the IBM Tivoli Storage
FlashCopy Manager repository. BKI1580E Specifying a target volume serial
number is mandatory for parameter
System action: Processing continues.
'TARGET_VOLUME'.
User response: None.
Explanation: The parameter 'TARGET_VOLUME'
expects three values being defined. If these are not
BKI1570W The following container could not be present this error occurs.
deleted from the storage box during
System action:
reconciliation: volume_name.
User response: Specify the following values for
Explanation: The volume volume_name could not be
parameter 'TARGET_VOLUME': <target volume serial
deleted from the storage box. It is not needed anymore
number> <source volume serial number> <source
because there is no corresponding backup in the
volume size>. Only the first value is mandatory. If
repository.
source volume information is omitted, dashes must be
System action: entered in both fields as placeholders. Examples:
TARGET_VOLUME 401FCA90 40EFCA90 Size=2.0_GB
User response: Ignore the warning or try to delete the TARGET_VOLUME 401FCA909 - -
volume from the storage device manually.

BKI1581E Error while parsing parameter

BKI1571W The specified value for 'recon_interval' is TARGET_VOLUME target volume param
0. Be aware that every time a in volumes file: the parameter
background monitor is started a TARGET_VOLUME allows at most
reconcile will be scheduled so that other three parameters.
background operations will never be
scheduled. This should be used for Explanation: The parameter 'TARGET_VOLUME'
testing purposes only. expects three values being defined. If there are more
this error occurs.
Explanation: If RECON_INTERVAL is 0 every time a
background monitor is started it will start System action:
reconciliation. Other background operations as deletion
User response: Correct the specified values for
or monitoring will never be scheduled.
parameter 'TARGET_VOLUME' according to this
System action: pattern: <target volume serial number> <source volume
serial number> <source volume size>. Only the first
User response: Change RECON_INTERVAL to a value value is mandatory. If source volume information is
greater than 0 if you want to avoid this behavior. omitted, dashes must be entered in both fields as
placeholders. Examples: TARGET_VOLUME 401FCA90
BKI1572I Starting reconciliation for device class 40EFCA90 Size=2.0_GB TARGET_VOLUME 401FCA909
'device_class_name' --

Explanation: The reconciliation will be started for the

device class device_class_name of the profile. BKI1582I The target set target set will be used for
the current backup.
System action:
Explanation: IBM Tivoli Storage FlashCopy Manager
User response: None. allows to define target sets by a target set definition file
(SVC and DS8000®) or by a certain naming convention
by that IBM Tivoli Storage FlashCopy Manager
determines the name of the target from the name of the
source volume and the name of the target set to be

18 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI1583W • BKI2007E

used for the current operation (SVC only). This the minimimum length and complexity requirements.
message reflects which target set is applied for the
current snapshot backup based on the given conditions.
BKI2000I Successfully connected to
System action: component_name on port portnumber.
User response: Specify means of target set selection by Explanation: One of the Data Protection for SAP
the profile parameter 'TARGET_SETS' and a target set modules BACKINT or theThe backup library libtdp_r3
definition file. initiated a successful connection to the background
process component_name on port portnumber.
BKI1583W Backup agents were requesting System action:
incompatible Tivoli Storage Manager
User response: None.
backup options. The composed states
are: 'states'.
BKI2001E Socket error while connecting to
Explanation: A backup of a partitioned database was
component_name at host: reason.
attempted. Offloaded backups to Tivoli Storage
Manager use options that are different from options Explanation: The background process component_name
used with the partition backup. However, Tivoli is not running.
Storage Manager backup options for all partitions
should be identical. This can occur when different System action:
device classes are used to back up different partitions, User response: Start component_name manually and try
and those device classes are associated with different again.
Tivoli Storage Manager backup options. The product
automatically determines the correct Tivoli Storage
Manager backup options for this operation to prevent a BKI2003I File file_name BID deleted.
failure. Explanation: The file file_name with the backup ID
System action: The operation continues with warning. <BID> was deleted from the Tivoli Storage Manager.

User response: Update the configuration so that all System action:

partitions use the same Tivoli Storage Manager backup User response: None.
options during future operations.

BKI2004E Socket error while listen to port port

BKI1586E Not enough sessions available. number - error: error text.
Explanation: The sum of available sessions specified Explanation: The application was unable to listen to
in the various server statements does not cover the the port specified.
required numbe r of sessions.
System action: Processing stops.
System action: Processing ends.
User response: Check if the process was already
User response: Change and adapt the values of the started. Do not start a second instance of the same
corresponding parameters in the IBM Tivoli Storage process. Check if the port specified is in use by another
Manager for Enterpri se Resource Planning profile. application and specifiy a different port number.

BKI1588E The master password you provided does BKI2007E Unknown Port: port
not meet the minimum complexity
requirements. Acceptable master Explanation: The port specified for communication
passwords are a minimum of minlength between component_name and BACKINT or the backup
characters and must contain at least one library is unknown.
number and one letter. System action:
Explanation: For security reasons, the master User response: Check the port value specified when
password must meet minimum length and complexity component_name was started. Additionally, check the
requirements. The master password must be a environment variable PROLE_PORT for the BACKINT
minimum of 8 characters and must contain at least one environment. These two values must match.
number and one letter. The use of special symbols
increases the strength of the password.
System action: The password you provided is not
adopted.
User response: Define a strong password that meets

Chapter 2. Tivoli Storage Manager for ERP messages 19

BKI2008E • BKI2026E

BKI2008E Unable to connect to component_name. BKI2015I Starting BACKEND program.

Explanation: Internal error. Explanation: The backend program is executing.
System action: System action:
User response: Contact IBM Support. User response: None.

BKI2009I Deleting backup version_number and all BKI2016I BACKEND program finished.
older backups.
Explanation: The backend program is finished.
Explanation: All full database backups and their
System action:
corresponding log file backups will be deleted from
Tivoli Storage Manager storage, if their version number User response: None.
is less than or equal to version_number.
System action: BKI2017I Blocksize is set to num_bytes bytes
User response: None. Explanation: The operational blocksize is num_bytes
bytes.
BKI2010E Error occurred processing FRONTEND. System action:
Explanation: An error occurred during the frontend User response: None.
processing.
System action: BKI2022E Unable to change mode of file file name:
description
User response: Check the frontend script/program
and the settings in the Data Protection for SAP profile Explanation: Unable to change mode of file file name.
(keyword FRONTEND) and try again. description may contain the system error text.
System action:
BKI2011E Error occurred processing BACKEND.
User response: Check the description. If the error
Explanation: An error occurred during the backend persists, contact your service representative.
processing.
System action: BKI2024E Error in connection to component_name.
User response: Check the backend script/program Explanation: The connection to component_name
and the settings in the Data Protection for SAP profile terminated unexpectedly. This message might be
(keyword BACKEND) and try again. displayed due to previous errors or after an unexpected
termination of the component_name process.
BKI2012E Passwords do not match. Try again. System action:
Explanation: The first and second password you User response: Check for other error messages and
entered do not match. restart component_name if necessary. Try again. If the
problem persists, contact IBM Support.
System action:
User response: Enter the password correctly.
BKI2025E Failed to respond to a message received
from component_name.
BKI2013I Starting FRONTEND program.
Explanation: This is an internal error.
Explanation: The frontend program is executing.
System action:
System action:
User response: Contact IBM Support.
User response: None.
BKI2026E Unexpected exception in handler:
BKI2014I FRONTEND program finished. handler.
Explanation: The frontend program is finished. Explanation:
System action: System action: This is an internal error.
User response: None. User response: Contact IBM Support.

20 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI2027I • BKI4005E

BKI2027I Using TSM–API version your API version BKI4000W The attributes of file 'file name' cannot be
(compiled with compiled with version). restored. Reason: errno(error_num)
error_desc.
Explanation: Version information about the TSM–API.
Explanation: The file file name was restored
System action:
successfully but one or more file attributes (permission,
User response: None. ownership, date/time) of the file file name cannot be
restored correctly.

BKI2028W Unable to terminate a session due to the System action:

following error:session.
User response: Check the error number error_num and
Explanation: This is an internal error during cleanup the error description error_desc to avoid this problem in
that has no effect on the success of the service. the future. An initial solution could be to set the
appropriate correct permission for the file file name
System action: manually.
User response: None.
BKI4001E File 'file name' cannot be created. Reason:
BKI2029E Could not instantiate the buffer errno(error_num) error_desc
allocator because of the following Explanation: The file file name to be restored could not
incompatibility issue: expression. be created/written. It is possible, that you do not have
Explanation: This is an internal error. the appropriate rights for writing the file file name to
the destination path.
System action:
System action:
User response: Contact IBM Support.
User response: Check the error number error_num and
the error description error_desc to avoid this problem in
BKI2031E A buffer allocator cannot the future. Furthermore, check the write permission of
simultaneously satisfy all of the the user who started the restore.
following properties:list of properties
Explanation: This is an internal error. BKI4002E Error during write of file ' file_name'.
System action: Reason: errno(error_num) error_desc

User response: Contact IBM Support. Explanation: An error occurs during the restore
process of the file file name.

BKI2033E Cannot instantiate allocator of type System action:

allocator type with the following User response: Check the error number error_num and
additional properties:list of properties the error description error_desc to avoid this problem in
Explanation: This is an internal error. the future.

System action:
BKI4005E Error allocating memory block for file
User response: Contact IBM Support. file name. BLOCKSIZE may be too large.
Explanation: Unable to request new memory blocks
BKI2913I The version delete setting is configured during the backup of file file name.
to retain number backup generations.
Checking for expired backups. System action:

Explanation: The profile parameter MAX_VERSIONS User response: Verify that you have set a valid value
is configured to retain number backup generations. Data for BLOCKSIZE. If you are not sure what value is
Protection for SAP is checking if surplus backups exist. valid, comment it out so the default value is used.
Furthermore, you can check if you have enough RAM
System action: Processing continues. available with your machine. Also, check the memory
User response: None. usage during backup. It may be necessary to stop
another application, increase memory, or change the
configuration.

Chapter 2. Tivoli Storage Manager for ERP messages 21

BKI4007E • BKI5002E

BKI4007E File 'filename' cannot be read Reason: BKI4012E Unexpected EOF for file 'filename' after
errno(error_num) error description reading number Bytes.
Explanation: Data could not be read due to some Explanation: The end of file was reached
system error. Check error description for further unexpectedly.
information. If this error recurs, this might indicate
System action:
some hardware problems.
User response: Check the logs for further information.
System action:
If the problem cannot be resolved contact your IBM
User response: Contact your system administrator. support personnel.

BKI4008E File 'filename' cannot be opened. Reason: BKI4013I CreateFile() with

errno(error_num) error_text dwFlagsAndAttributes='attribute'.
Explanation: Could not open the file file name due to Explanation: A file with the nmed attribute was
some system specific problems. created.
System action: System action:
User response: Contact your system administrator. User response: None.

BKI4009E Not enough space to write File 'filename'. BKI4014E File 'filename' cannot be accessed.
Possible reasons: disk full or ulimit Reason: errno<(number) errormsg
exeeded.
Explanation: A named file could not be accessed
Explanation: The system rejected a request to write either for reading or writing.
data into file file name. The storage media might not
System action:
have enough free space to keep the file or the system
rejected writing the file due to administrative resource User response: Check the file permissions and if
constraints such as ulimits. necessary adjust them accordingly. Try again.
System action:
BKI5000E Tivoli Storage Manager
User response: Contact your system administrator.
Error:error_message
Explanation: During a connection of Data Protection
BKI4010E SAP requires the file filename to be a
for SAP to Tivoli Storage Manager server, a Tivoli
regular file.
Storage Manager error error_message occurred.
Explanation: To be able to support SAP environments
System action:
the named file has to be a regular file.
User response: Use the Tivoli Storage Manager
System action:
Messages guide and correct the Tivoli Storage Manager
User response: Check the logs for further information. server error. Try your last action again.
If the problem cannot be resolved contact your IBM
support personnel.
BKI5001E Tivoli Storage Manager
Error:error_message
BKI4011W The backup device type (filetype backup
Explanation: During a connection of Data Protection
devicetype backup devsubtype) differs from
for SAP to Tivoli Storage Manager server, a Tivoli
the restore device type (filetype restore
Storage Manager error error_message occurred.
descr1 descr2) for name.
System action:
Explanation: A mismatch between the device types
during backup and restore was detected. User response: Use the Tivoli Storage Manager
Messages guide and correct the Tivoli Storage Manager
System action:
server error. Try your last action again.
User response: Check the logs for further information
BKI5002E Tivoli Storage Manager Error during
inquire of mux file
backup_id:error_message
Explanation: See BKI5001E.
System action:

22 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI5003E • BKI5015W

User response: See BKI5001E.

BKI5010E Tivoli Storage Manager
Error:error_message
BKI5003E Tivoli Storage Manager
Explanation: See BKI5001E.
Error:error_message
System action:
Explanation: See BKI5001E.
User response: See BKI5001E.
System action:
User response: See BKI5001E.
BKI5011E Tivoli Storage Manager
Error:error_message
BKI5004W Tivoli Storage Manager
Explanation: See BKI5001E.
Error:error_message
System action:
Explanation: See BKI5001E.
User response: See BKI5001E.
System action:
User response: See BKI5001E.
BKI5012E Cannot open Tivoli Storage Manager
API message text file. Check if
BKI5005E Tivoli Storage Manager Error. DSMI_DIR is set correctly. Current
value of DSMI_DIR is: dsmi dir
Explanation: See BKI5001E.
Explanation: The Tivoli Storage Manager API is
System action: unable to open the message text file. This file is
User response: See BKI5001E. required in order to issue messages. By default, it
should reside in the Tivoli Storage Manager API
installation directory. If the Tivoli Storage Manager API
BKI5006E Tivoli Storage Manager is installed in another location, use the DSMI_DIR the
Error:error_message environment variable to specifiy the correct location.
Explanation: See BKI5001E. System action: Processing stops.
System action: User response: Verify that the DSMI_DIR environment
User response: See BKI5001E. variable points to the correct location and that the
Tivoli Storage Manager API installation is complete.

BKI5007E Tivoli Storage Manager Error.

BKI5013E Value for name is too long. Current
Explanation: See BKI5001E. value: value
System action: Explanation: The value of the environment variable
User response: See BKI5001E. name has too many digits.
System action:
BKI5008E Tivoli Storage Manager Error. User response: Check if the variable is set correctly.
Explanation: See BKI5001E.
System action: BKI5014E Tivoli Storage Manager
Error:error_message
User response: See BKI5001E.
Explanation: See BKI5001E.

BKI5009E Tivoli Storage Manager System action:

Error:error_message User response: See BKI5001E.
Explanation: See BKI5001E.
System action: BKI5015W Data description, file name could not be
restored, because it was backed up with
User response: See BKI5001E. a newer version (objInf_support
information).
Explanation: The TSM server hosts backups (data
description) which were made with a new version of
backint or backom, which ignores this data in further
processing.

Chapter 2. Tivoli Storage Manager for ERP messages 23

BKI5016I • BKI6911E

System action:
BKI5021W No data is deleted on the TSM Server
User response: Upgrade the product. because the environment variable
"XINT_FUNCTION_DELETE" is set to
"DISABLE".
BKI5016I Time: current time New TSM session
created: MGMNT–CLASS: Explanation: The delete function was disabled
management_class, TSM–Server: temporarily.
server_name, type: session_type
System action:
Explanation: A new session to TSM server server_name
User response: If the delete function has to be
has been established at current_time. Data will be stored
re–activated, unset the environment variable
in management class management_class.
XINT_FUNCTION_DELETE and try again.
System action:
User response: None. BKI5022W Error during version delete. Not all
backups that should have been expired
could be removed.
BKI5017E Internal Tivoli Storage Manager Error:
Transaction succeeded although it was Explanation: The database backup finished
expected to fail. successfully. Nevertheless, the deletion of expired
backup sets failed.
Explanation: An internal Tivoli Storage Manager error
occurred. System action:

System action: User response: Check the logs for further information.
If the problem cannot be resolved contact your IBM
User response: Retry the action. If the error occurs support personnel.
again contact IBM Support.

BKI6199E Failed to determine the database id.

BKI5018E The requested buffer has a size Output of the failed command:output
(current_size bytes) that is smaller than
requested requested_size. Explanation: The attempt to determine the database id
was unsuccessful. Requirements for this operation are a
Explanation: The request for a new buffer was complete and functional database software installation
successful. The buffer, however, does not have the and a valid control file.
requested size.
System action: Processing stops.
System action:
User response: Check the output of the failed
User response: Check if the system is running low on command for further information about the root cause.
memory and retry the action. If the error occurs again Resolve these issues and perform the operation again.
contact IBM Support.

BKI6910E Could not set user ID to userid. Error

BKI5019E Error during delete of object error – errormsg.
filename:object
Explanation: The user id of the device agent process
Explanation: A named file could not be deleted from a could not be switched internally to the named user id.
TSM server.
System action:
System action:
User response: Check the permissions of the binary
User response: Check the logs for further information. and try again.
If the problem cannot be resolved contact your IBM
support personnel.
BKI6911E The effective user ID userideff of the
process could not be set to the user
BKI5020E Error while deleting objects :objects userid. Error error – error_msg. Check that
Explanation: One or more named objects could not be the device agent executable has the s–bit
deleted from a TSM server. set.

System action: Explanation: Due to insufficient permissions of the

device agent executable, the user id of the device agent
User response: Check the logs for further information. process could not be switched internally to the named
If the problem cannot be resolved contact your IBM user id.
support personnel.
System action:

24 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI7048I • BKI7060I

User response: Check that the device agent binary has

BKI7056E Service open failed because configured
the s–bit set and try again.
TSM server could not be accessed.
Explanation: The command could not be started
BKI7048I The default port to connect to
because the TSM server defined in the profile could not
server_name will be used.
be accessed.
Explanation: A server port for the connection to the
System action:
named server was not explicitly specified. Therefore,
the default port is used. User response: Check the product log file for further
detailed messages.
System action:
User response: Make sure the named server is
BKI7057E Service open failed because all
listening to the default port. In the case of connection
configured sessions are currently in use.
failures, specify the server port in the profile.
Explanation: The command could not be started
because all configured sessions in the profile are
BKI7049I The default for environment variable
currently in use.
PROLE_PORT will be used.
System action:
Explanation: The port for the internal communication
of Data Protection for SAP is set during installation. User response: With Oracle RMAN the number of
The message indicates that this port is being used. channels configured either in SAP profile or the RMAN
script must be less or equal to the maximum number of
System action:
allowed sessions (MAX_SESSIONS). If multiple servers
User response: None. are used see the User's Guide for further details. Also
check the Data Protection for SAP log file for further
detailed messages.
BKI7051E The environment variable
XINT_PROFILE is not set. It must be set
and contain the fully qualified path to BKI7058E Service open failed because more than
the *.utl file to be used. one file was found with the same name.
Explanation: The way Data Protection for SAP works Explanation: The command could not be started
is specified in a profile. When called, Data Protection because two or more files with the same name were
for SAP looks for the environment variable found.
XINT_PROFILE which must contain the fully qualified
System action:
path to the profile.
User response: Check the product log file for further
System action:
detailed messages.
User response: Check the environment for
XINT_PROFILE of the user who started Data Protection
BKI7059E Service open failed because the file was
for SAP.
not found.
Explanation: The command could not be started
BKI7053E Service setup failed due to previous
because a file specified was not found.
error.
System action:
Explanation: Initialization of the product failed due to
previous errors. User response: Check the product log file for further
detailed messages.
System action:
User response: Check the product log file for further
BKI7060I Data Protection for SAP(R)
detailed messages.
version.release.modification.level (build
build_number)beta build_date session:
BKI7055E Service open failed due to previous process id
error in data mover.
Explanation: This message is to verify the version of
Explanation: The command could not be started due the shared library used for backup. On UNIX and
to previous errors. Linux systems this message will be written multiple
times into the log per backup depending on the RMAN
System action: setup. On Windows, it is written just once.
User response: Check the product log file for further System action:
detailed messages.

Chapter 2. Tivoli Storage Manager for ERP messages 25

BKI7061I • BKI7305E

User response: None, if the right version is used. If

BKI7064W Seems the previous operation was not
the version within the log does not match the installed
completed successfully. Cleaning up.
version, see 'RMAN Problem Resolution' in the Data
Protection for SAP(R) Installation and User's Guide. Explanation: Internal states indicate that an operation
is still running while a new one has started. This may
be caused by database processes that did not terminate
BKI7061I Continuing to restore from next data
correctly. Data Protection for SAP is going to clean up
copy.
these internal states to avoid potential problems.
Explanation: A saved data copy could not be restored
System action: Processing continues.
from the primary data source. Due to multiple data
copies available, the unit will switch to the next User response: Check if any database processes from
available data copy and continue to restore. previous backup or restore operations are still active.
Consult the users guide of the database about how to
System action:
clean up such processes.
User response: Although the data could be restored it
should be investigated, why one of the data sources
BKI7301W Data exchange file from Data Protection
were not available.
for Snapshot Devices for SAP, filename
does not exist.
BKI7062E To create number_copies redo log copies
Explanation: The referenced file is expected by Data
at least number_sessions sessions and
Protection for SAP(R) to exist and to contain
number_mgmtclasses different
information from Data Protection for Snapshot Devices
BRARCHIVE management classes are
for SAP(R) about the actual snapshot operation.
required. But currently only
configured_sessions sessions are available. System action:
Explanation: If each redo log file should be stored User response: The absences of this files indicates a
multiple times then for each copy a dedicated session problem during the snapshot operation performed by
and management class at the Tivoli Storage Manager Data Protection for Snapshot Devices for SAP(R). Please
server is required. Currently there are more redo log check the logs of DP for Snapshot Devices for SAP(R)
copies requested with the profile parameter to determine the cause of the problem and try again.
REDOLOG_COPIES than sessions and/or management
classes are available.
BKI7303W Profiles for Data Protection for Snapshot
System action: Processing ends. Devices for SAP are different. backup:
file name backup restore: file name restore
User response: Check the profile parameter
MAX_ARCHIVE_SESSIONS or if not set check the Explanation: During backup the profile used by DP
value of parameter MAX_SESSIONS. Increase the value for Snapshot Devices can be determined automatically.
to be at least as large as number_copies. Ensure the For restore and inquire operations the profile for DP for
overall number of sessions and management classes Snapshot Devices must be specified in the profile using
that are configured over all server stanzas in the Data the parameter FCS_FILE. For restore DP for Snapshot
Protection for SAP profile is at least as large as Devices must use the same profile as for backup.
number_copies.
System action:
User response: Correct the entry for the FCS_FILE
BKI7063W The profile parameter
parameter in the profile (init<SID>.utl).
BACKUPIDPREFIX is no longer valid
for Data Protection for SAP HANA and
will be ignored. BKI7304I Performing DISK ONLY backup.
Explanation: Starting with version 6.4.1.1 it is no Explanation: The data for this backup is stored on
longer possible to specifiy the backup ID prefix for snapshot–type disks only and will not be sent to TSM.
Data Protection for SAP HANA. The first six characters
of the backup ID are now generated automatically. System action:

System action: Processing continues. User response: None.

User response: Remove the parameter

BACKUPIDPREFIX from the profile. BKI7305E Error during call to Data Protection for
Snapshot Devices for SAP: error message
Explanation: DP for Snapshot Devices could not
process the requested operation successfully. Processing
may not stop at this point. Depending on the type of

26 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI7307W • BKI7314E

request (backup to both TSM and snapshot disks or to System action:

snapshot disks only, restore of data which is available
User response: Enter 'stop' if you want to terminate
in both modes) there are possibilities to recover from
this restore process. Enter 'cont' if you want to retry the
this error and continue operation.
snapshot process.
System action:
User response: Use the information from error message BKI7311I Profile used by Data Protection for
and the output of DP for Snapshot Devices to Snapshot Devices for SAP: profile name.
determine the cause of the problem and try again.
Explanation: The message shows the name of the
profile used by DP for Snapshot Devices.
BKI7307W Data Protection for Snapshot Devices
System action:
for SAP reported an error during a
snapshot–type operation.Do you want to User response: None.
continue backing up to TSM?
Explanation: The backup was requested to be stored BKI7312W Profile for Data Protection for Snapshot
on both the TSM server and the snapshot–type disks. Devices for SAP not specified in profile.
The snapshot operation has failed. Backup can continue For restore this must be specified.
to save data on the TSM server only.
Explanation: For restore and inquire operation in
System action: conjunction with DP for Snapshot Devices this
parameter is mandatory. Without this parameter a
User response: Enter 'stop' if you want to solve the
restore using DP for Snapshot Devices is not possible
cause of this error and to try again. Enter 'cont' if you
and Data Protection for SAP will continue to
want to save this data on the TSM server only.
inquire/restore from the TSM server only.
System action:
BKI7308E DISK ONLY backup has failed.
User response: Add the parameter FCS_FILE to the
Explanation: The current backup tried to store data on
Data Protection for SAP profile.
snapshot–type disks only and did not finish
successfully.
BKI7313W Inquire results from Data Protection for
System action:
Snapshot Devices for SAP are not
User response: Check the output from DP for available.
Snapshot Devices prior to this error message to detect
Explanation: Data Protection for SAP queried Data
the root cause of this error and try again.
Protection for Snapshot Devices for SAP for existing
snapshot backups. This query has failed.
BKI7309W Data Protection for Snapshot Devices
System action: Processing continues.
for SAP reported an error during a
snapshot–type operation.Do you want to User response: If Data Protection for SAP is running
continue restoring from TSM? in unattended mode (profile parameter BATCH set to
YES), it immediately restores from tape when data is
Explanation: The data you wanted to be restored is
available. Otherwise you are prompted whether to
located on the TSM server and on snapshot–type disks.
restore from tape.
The snapshot operation has failed. The process can
continue to restore data from the TSM server.
BKI7314E The data you want to restore is not
System action:
available on the TSM server.
User response: Enter 'stop' if you want to resolve the
Explanation: Data Protection for SAP(R) was unable
cause of this error and to try again. Enter 'cont' if you
to retrieve information from DP for Snapshot Devices
want to restore from the TSM server.
about available backups on snapshot–type disks. This
message may be issued in consequence of message
BKI7310W Data Protection for Snapshot Devices BKI7305E.
for SAP reported an error during a
System action:
snapshot–type operation.CAUTION: Not
all filesystems are available.Do you User response: Check the output from DP for
want to retry the operation? Snapshot Devices to determine the cause of the error
and try again.
Explanation: In contrast to message BKI7309W not all
file systems are mounted. In this case it is not possible
to continue the restore from the TSM server.

Chapter 2. Tivoli Storage Manager for ERP messages 27

BKI7315W • BKI7323W

BKI7315W The copy process for the files you want BKI7321E The Data Protection for Snapshot
to restore is not finished. If you Devices for SAP profile file name found
continue the operation, the files will be in parameter FCS_FILE of the DP for
restored from the TSM server. SAP(R) profile can not be used if you
need to restore this backup.
Explanation: The snapshot process running in the
background has not finished moving the files from the Explanation: In the Data Protection for SAP profile the
source to the target volumes. A snapshot restore of FCS_FILE parameter is set, however the Data
these volumes is currently not possible. Protection for Snapshot Devices for SAP profile
specified either v is not a Data Protection for Snapshot
System action:
Devices for SAP profile v does not point to the same
User response: After that message you will be asked if Data Protection for Snapshot Devices for SAP
you want to continue or stop this operation. If you configuration file which was used by the preceding
want to wait until the snapshot process has finished Data Protection for Snapshot Devices for SAP splitint
choose 'stop' and the restore attempt will terminate. If operation.
you choose 'continue' an attempt is made to restore the
System action:
data from TSM if available.
User response: You need v to correct the FCS_FILE
parameter in order to ensure that a valid Data
BKI7316I The following backup types for the
Protection for Snapshot Devices for SAP profile is used.
BACKUPID backup id have been found:
For example, select the same file Data Protection for
– TSM – Snapshot
Snapshot Devices for SAP used when running its
Explanation: The backup for the backup ID Backup ID snapshot function in the preceding brbackup task. The
was stored on the Tivoli Storage Manager as well as on file names are documented in preceding message
snapshot–type disks. For restore both data sources can BKI7303W) v to ensure that all SAP profiles used by
be used. Data Protection for Snapshot Devices for SAP point to
the same the same control file. The control file is
System action: defined by the value of the IDS_CONTROL_FILE
User response: None. parameter in the Data Protection for Snapshot Devices
for SAP profile.

BKI7318E The Data Protection for Snapshot

Devices for SAP profile file name is not BKI7322E Request for a partial restore or restore
valid. from snapshot with "brrestore –m all" is
not supported. In case of brrestore
Explanation: The profile for DP for Snapshot Devices attempt rerun with –m full.
specified in init<SID>.utl could not be accessed.
Explanation: DP for Snapshot Devices can only restore
System action: the whole content of a backup and not only a subset of
User response: Check the file name and the a disk backup as requested. Most likely this is caused
permissions for this file and try again. by running brrestore with the option '–m all'.
System action:
BKI7319I Start TSM restore. User response: Restore complete backups only: run
Explanation: The restore uses data from Tivoli Storage brrestore with the option '–m full'.
Manager.
System action: BKI7323W Request for a partial restore or restore
from snapshot with "brrestore –m all" is
User response: None. not supported. If you want to restore the
backup: – with FlashCopy restore enter
BKI7320I Start restore from snapshot. stop and rerun brrestore with "–m full"
– from TSM enter cont
Explanation: The restore is using data from
snapshot–type disks. Explanation: This message has the same reason as
message BKI7322E, but in this case the data is also
System action: available from the TSM server. So you may continue to
restore this data without the snapshot functionality
User response: None.
from TSM server.
System action:
User response: Enter 'stop' if you want to try to
restore a different set of files. Enter 'cont' if you want to

28 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI7324E • BKI7545I

restore this data from TSM server.

BKI7541E The environment variable ORACLE_SID
must be set.
BKI7324E Restore of multiple backup ID's in one
Explanation: The current operation requires the
run from a snapshot is not possible.
environment of the Oracle database instance owner.
Explanation: The data requested for this restore Among other settings this includes the environment
belongs to multiple backup IDs. variable ORACLE_SID.

System action: System action: Operation aborts.

User response: Make sure the files you want to restore User response: Ensure the operation is performed by
belong to one single backup ID and try again. the Oracle database instance owner and verify that the
environment for this user is set correctly. Among other
environment variables that are required to run an
BKI7325E Redirected restore from a snapshot is Oracle database the variable ORACLE_SID must be set.
not possible.
Explanation: A restore of a snapshot to a different BKI7542I A level number incremental backup
location on the same host was attempted. This is not using Oracle RMAN has started.
supported.
Explanation: Oracle RMAN will be started to perform
System action: Processing stops. an incremental backup with the specified level.
User response: Either restore the snapshot to the System action: Operation continues.
original location or restore from tape (if available).
User response: None.
BKI7535W Error while executing command. Reason:
errno(error number) explanation BKI7543I Recreate database control file 'file_name'.
Explanation: A command could not be executed Explanation: CURRENTLY UNUSED
successfully.
System action: Operation continues.
System action:
User response: None.
User response: Check the explanation explanation and
the preceding output of the command execution to
BKI7544E The copy of the database control file
detect the cause of the error.
'file_name' was not found.
Explanation: The current operation does expect a copy
BKI7536I Execute command 'command name':
of the database controlfile to be at the specified
Explanation: The command command name is executed location. This file is created by IBM Tivoli Storage
by the application. This message is followed by the FlashCopy Manager before Data Protection for SAP is
output of the command executed. started. But the file was not found.

System action: System action: Operation aborts.

User response: None. User response: Verify that the target directory does
exist and is not full. Make sure that the directory is not
cleaned automatically at the time of the operation.
BKI7540E None of the INCREMENTAL_LEVEL
parameters specified in the profile can
be used for the current operation. BKI7545I Please enter the password for the user
'user_name' to connect against the
Explanation: The application of a recovery catalog database
'INCREMENTAL_LEVEL' entry within the profile can 'catalog_database_identifier':
be restricted by a number of optional conditions, e.g.
by time frame. If this error occurs none of the Explanation: Oracle RMAN stores information about
INCREMENTAL_LEVEL entries within the profile all backups in a recovery catalog database. The
matches the conditions currently given (current time, identifier to connect against this database and the user
given weekday). id for this connection must be specified in the profile.
The password for this connection must be specified
System action: after this prompt. It is then stored encrypted in the
User response: Check the conditions specified for the configuration file.
'INCREMENTAL_LEVEL' entries within your profile. It System action: Wait for user response.
needs to be ensured that exactly one entry matches any
imaginable condition at any time. User response: Enter the correct password.

Chapter 2. Tivoli Storage Manager for ERP messages 29

BKI7546E • BKI7555E

BKI7546E Failed to verify the password. This is BKI7551E Failed to determine the database ID:
the output of the failed command:
Explanation: The process failed to determine the id of
Explanation: The verification of the password entered the database in the recovery catalog database.
has failed. This may be due to missconfiguration of the
System action: Operation aborts.
connection to the recovery catalog database or just by
misstyping the password. User response: Check the log output following this
message for more details about the root cause of this
System action: Operation aborts.
error.
User response: Check the further ouput to find the
root cause. Retry the operation and enter the correct
BKI7552E Failed to determine the SCN:
password.
Explanation: The process failed to determine the
restore point in time in the recovery catalog database.
BKI7547E Failed to verify the password. This is
the output of the failed command: System action: Operation aborts.
Explanation: User response: Check the log output following this
message for more details about the root cause of this
System action: Operation aborts.
error.
User response:
BKI7553I Restoring files from backup with ID
BKI7548E Incremental backups require IBM Tivoli backup_ID using Oracle RMAN ...
Storage FlashCopy Manager V3.1 or
Explanation: Oracle RMAN was started to restore all
higher.
datafiles from the backup identified by backup_ID.
Explanation: To perform offloaded backups using
System action: Operation continues.
Oracle RMAN the offload operation must be performed
using IBM Tivoli Storage FlashCopy Manager Version User response: None.
3.1 or higher.
System action: Operation aborts. BKI7554E The password to connect against the
recovery catalog database 'identifier' is
User response: Ensure the required version of IBM
not set.
Tivoli Storage FlashCopy Manager is installed and
configured. Explanation: The password for the recovery catalog
database was not found in the config file. It is stored in
encrypted form in the config file. To store the password
BKI7549E Database 'identifier' is still running on
in the config file the function '$ndash;f
host 'host_name'.
catalog_password' must be used.
Explanation: Another instance of the database was
System action: Operation aborts.
found to be running on the backup server where the
offloaded backup should be performed. User response: Run 'backint –p <profile> $ndash;f
catalog_password' to store the password in the config
System action: Operation aborts.
file. Then retry the operation.
User response: Verify the configuration if the
offloaded backup was attempted on the correct backup
BKI7555E Files from different RMAN backups can
server. Check if the running database instance is a
not be restored within a single
leftover from a previous backup attempt. In this case
operation.
manually shutdown the instance and retry.
Explanation: The current operation attempted to
restore files that have been stored by RMAN in
BKI7550E Operation was cancelled by Oracle
different backups. This type of restore is not supported.
RMAN. Please check the log for more
details. System action: Operation aborts.
Explanation: The operation was cancelled by Oracle User response: If files from different backups are
RMAN. required only the files from one backup can be restored
at a time. Restore files from other backups in separate
System action: Operation aborts.
runs.
User response: Check the log output preceeding this
message for more details about the root cause of this
error.

30 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI7556E • BKI8307E

Explanation: The named product implementing the

BKI7556E Restore of RMAN backups to a different
DB2 Advanced Copy Services API received an error in
location is not supported.
the named API function. The error information is
Explanation: The current operation attempted to shown.
restore database files to a location that is different from
System action:
the location at backup time. This type of restore is not
possible with backups that have been performed by User response: Analyze the error information and the
Oracle RMAN from a flashcopy backup. appropriate log files to find the cause of the problem.
Resolve any problems indicated.
System action: The operation stops.
User response: Restore the files to the same location
BKI8303E No segment_name section found for the
from where they have been backed up. If you want
instance 'id'.
create a clone of the database, use the $longfcm;
cloning functionality. Explanation: An error was detected while parsing the
named profile segment name section.
BKI8201E SIMULATION CANCELED BY System action:
PRODUCTION OPERATION!!!
User response: Check the named profile segment
Explanation: The current operation was a simulation name section and make appropriate adjustments.
performed via the Administration Assistant. This
simulation was canceled since a production operation
(backup or restore) has been started. BKI8304W The following error occured while
verifying the configuration for section
System action: 'section':
User response: Check your backup schedule and run Explanation: An error was detected while parsing the
simulations only when no other operations are named profile section.
scheduled.
System action:

BKI8300I Function_name returned with code User response: Check the named profile section and
return_codereturn_information. make appropriate adjustments.

Explanation: This message indicates that the named

API function ended with the specified return BKI8305E Invalid option option in options string:
information. 'options_string'.

System action: Explanation: An invalid option was found while

parsing the options string specified in the 'db2'
User response: If the return information indicates a command.
problem, look for preceding error messages in the log
files. Otherwise, no response is required. System action:
User response: Correct the command and try again.
BKI8301E Product_name: Exception caught in
function function_name. Error BKI8306E The keyword keyword is not allowed
information: 'error_information' multiple times within the profile.
Explanation: The named product implementing the Explanation: The keyword indicated was found more
DB2 Advanced Copy Services API received an error in than once in the profile. However, this keyword must
the named API function. The error information is not be specified multiple times.
shown.
System action:
System action:
User response: Correct the profile.
User response: Analyze the error information to find
the cause of the problem. Resolve any problems
indicated. BKI8307E The parameter keyword must be specified
in the profile.

BKI8302E Product_name: Exception caught in Explanation: A required keyword is missing in the

function function_name. More profile.
information may be available in file System action:
log_file_name. Error information:
'error_information' User response: Correct the profile.

Chapter 2. Tivoli Storage Manager for ERP messages 31

BKI8308E • BKI8318E

User response: Contact your IBM support personnel.

BKI8308E Single argument required for parameter
keyword.
BKI8314E Product_name: interface problem in
Explanation: The keyword indicated requires a single
function function_name: The session is
value. However, two or more values are found in the
already in use by a different operation.
profile.
Explanation: The named product detected an interface
System action:
problem in the named API function. Either the session
User response: Correct the profile. handle is used for various operations simultaneously,
or the functions are called in an order not supported by
the current version of the library.
BKI8309E Missing argument for parameter
keyword. System action:
Explanation: In the profile, a value is missing for the User response: Contact your IBM support personnel.
named parameter.
System action: BKI8315E Function_name: The following object is
not under the control of product_name:
User response: Correct the profile.
path
Explanation: The named product implementing the
BKI8310E The keyword keyword is not allowed.
DB2 Advanced Copy Services API detected a problem
Explanation: An invalid keyword was detected in the in the named API function: The path passed by the
profile. database is not under the control of the product.

System action: System action:

User response: Correct the profile. User response: Make sure the database to be backed
up meets the requirements for employing snapshot
backups.
BKI8311E For parameter keywortd, both server and
port must be specified.
BKI8316E Product_name: interface problem in
Explanation: A value of the named parameter is function function_name: Empty group list
missing from the profile. passed by DB2.
System action: Explanation: The named product detected an interface
User response: As the value for the specified problem in the named API function: The database
parameter, specify both server and port. passed a group list containing no elements.
System action:
BKI8312E Error while parsing parameter keyword. User response: Contact your IBM support personnel.
In order for 'value1' to be valid 'value2' is
required to be an existing directory.
BKI8317W Product_name: Verification of
Explanation: Value1 was found to be an invalid value configuration requested by user. No
for the parameter named. For this specific parameter, a backup started.
file name can be specified whose path must already
exist in the system. Explanation: The user requested a verification of the
configuration. The backup flow continued without
System action: errors up to the point where the snapshot would
User response: Specify the name of a file in an actually be done and was then cancelled. The system is
existing path. ready for a snapshot backup, but no action beyond
verification has been taken so far.

BKI8313E Product_name: interface problem in System action:

function function_name: Invalid value of User response: None.
parameter: value
Explanation: The named product detected an interface BKI8318E Product_name: interface problem in
problem in the named API function. An invalid value function function_name: Not enough
was found for parameter in one of the API data space provided to write meta data.
structures.
Explanation:
System action:
System action:

32 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8319W • BKI8327E

User response: Contact your IBM support personnel.

BKI8323E Product_name: Problem occurred while
processing function_name. Please check
BKI8319W Error while deleting old versions.This log file log_file_name for more
problem does not affect the new information. Error information:
backup.Error information: 'error_information'
'error_information'
Explanation: The named product implementing the
Explanation: After a successful backup, the system DB2 Advanced Copy Services API received an error in
tries to remove older backups of the database according the named API function. The error information is
to the value of profile parameter MAX_VERSIONS. shown.
However, a problem occurred while trying to remove
System action:
expired backups. The new backup is not affected by
this problem. User response: Analyze the error information and the
appropriate log files to find the cause of the problem.
System action:
Resolve any problems indicated.
User response: Check the appropriate log files in
order to determine the cause of the problem. Resolve
BKI8324E Product_name: Problem occurred while
any problems indicated. In case the storage device runs
processing function_name: Device agent
out of storage because outdated snapshot backups have
returned code return_information.
not been removed, delete these snapshot backups
manually. Explanation: The named product implementing the
DB2 Advanced Copy Services API received an error
from the device agent in the named API function. The
BKI8320I Deleting full backup backup_id –
device agent's return information is given.
backup_key.
System action:
Explanation: After a successful backup, the system
tries to remove older backups of the database according User response: Check the appropriate log files to find
to the value of profile parameter MAX_VERSIONS. the cause of the problem. Resolve any problems
During this process, the full backup listed is removed. indicated.
System action:
BKI8325E Failed to determine hostname.
User response: None.
Explanation: The system was not able to determine
the host name of the machine.
BKI8321I Deleting partial backup backup_id for
node host:partition_number. System action:
Explanation: After a successful backup, the system User response: Make sure the system setup allows for
tries to remove older backups of the database according querying the hostname via system function
to the value of profile parameter MAX_VERSIONS. gethostname(). Ensure that the requirements for doing
During this process, the backup listed for the named snapshot backups are met.
partition is removed.
System action: BKI8326E Failed to create log directory path.
User response: None. Explanation: The log path indicated is not available in
the system and could also not be created.
BKI8322E Interface problem: Current database System action:
partition number is not listed in the
User response: Check the properties of the path
partition list.
indicated and make sure that its properties and the
Explanation: The partition list passed by the database properties of the parent directory are set accordingly.
does not contain the named partition participating in Make sure all prerequisites for doing snapshot backups
an operation. are met.
System action:
BKI8327E Invalid value specified for parameter
User response: Contact your IBM support personnel.
keyword: value
Explanation: A parameter value is not valid.
System action:
User response: In case the parameter was specified in

Chapter 2. Tivoli Storage Manager for ERP messages 33

BKI8328E • BKI8338E

the profile correct the profile. In case the parameter was User response: Correct the profile or the call as
specified as a command line option, correct the entry. appropriate.

BKI8328E Product_name must be licensed to set BKI8334E Profile section section_name is required
parameter keyword to a value of value. for function operation.
Explanation: Selected functions are supported only Explanation: The specified profile section is required
with a full TSM license. in order to perform the requested operation. However,
it is not included in the profile.
System action:
System action:
User response: If you need the functionality
requested, obtain a full TSM license and install the User response: Correct the profile.
license file. Otherwise, in case the parameter was
specified in the profile, correct the profile or, in case the
BKI8335E Profile section section_name refers to a
parameter was specified as a command line option,
value for keyword that differs from the
correct the entry.
one used at backup time. Expected
value: value.
BKI8330E Parameter keyword requires 'YES', 'NO',
Explanation: The profile parameter named must not
or AUTO.
change its value between backup and restore. However,
Explanation: For the named parameter, only the in the named profile section, the parameter has a value
values, 'YES', 'NO' and 'AUTO' are accepted. different from the value it had at backup time. This
value is given in the message.
System action: Processing stops.
System action:
User response: Correct the profile or the call as
appropriate. User response: Correct the profile by setting the
indicated parameter to the value indicated in the
message.
BKI8331E The parameter keyword1 is not allowed if
keyword2 is set to value.
BKI8336E Invalid value specified for option
Explanation: There is a dependency between
keyword: value
parameters keyword1 and keyword2. If the latter is set to
the value named, keyword1 must not be specified. Explanation: An option value is not valid.
System action: System action:
User response: Correct the profile or the call as User response: Correct the call.
appropriate.
BKI8337E Error while parsing profile: Missing
BKI8332E Failed to parse parameter keyword. File section name.
and path names in the profile need to
Explanation: The profile is organized into named
be fully qualified.
sections. However, a section name was not found.
Explanation: As the value of the parameter indicated,
System action:
a fully qualified file or path name is expected.
However, the specified value is not a fully qualified User response: Check that the profile name is
path. specified correctly or that the default profile is a valid
profile. Refer to your user documentation for the syntax
System action:
of the profile or use the profile wizard to create a new
User response: Correct the profile or the call as profile.
appropriate.
BKI8338E Error while parsing profile: Section
BKI8333E In order to enable the parameter section_name is not allowed to be nested.
keyword1 you need to set keyword2 to
Explanation: In the profile, the named section starts
value.
before the previous section ends. However, the section
Explanation: There is a dependency between in question cannot be nested.
parameters keyword1 and keyword2. If keyword1 is
System action:
specified, keyword2 must be given the specific value
indicated in the message. User response: Correct the profile.
System action:

34 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8339E • BKI8352E

BKI8339E Error while parsing profile: Profile BKI8345E Error while parsing parameter keyword.
section section_name is not valid. 'path' is required to be type_information.
Explanation: An invalid section name was found in Explanation: A path of the type indicated in the
the profile. message is expected as a value of the named parameter.
However, the specified path was not found to be of the
System action:
correct type.
User response: Correct the profile.
System action:
User response: Correct the profile or the call as
BKI8340E Error while parsing profile: Profile
appropriate.
section section_name must not be
specified more than once.
BKI8349I Deleting incomplete backup backup_id –
Explanation: In the profile, only a single section with
backup_key.
the name indicated can be specified. However, during
parsing, a second occurrence was detected. Explanation: After a successful backup, the system
tries to remove older backups of the database according
System action:
to the value of profile parameter MAX_VERSIONS.
User response: Correct the profile. During this process, the incomplete backup listed is
removed. A backup becomes incomplete when parts of
its data expire. This can happen when a backup that is
BKI8341E Error while parsing profile: Profile marked 'destructively restorable' is restored.
section section_name missing.
System action:
Explanation: The required profile section indicated
was not found in the profile. User response: None.

System action:
BKI8350E Parameter parameter requires 'NO',
User response: Correct the profile. 'TSM', or 'DP4SAP'.
Explanation: The value specified for the named
BKI8343W The profile parameter keyword profile parameter does not comply with the defined range of
parameter of device type provile section has values.
changed its value from (original)value1 to
(current) value2. System action:
Explanation: The profile parameter named must not User response: Check the named profile keyword and
change its value between backup and restore or delete. make appropriate adjustments.
However, in the named profile section, the parameter
has a new value value2 different from the value value1
BKI8351E Parameter parameter requires 'AUTO' or
it had at backup time. Both values are given in the
a decimal value.
message.
Explanation: The value specified for the named
System action:
parameter does not comply with the defined range of
User response: Check the log file for problems that values.
may result from the change of parameter values. If so,
System action:
you may want to change the profile, restoring
parameter profile parameter keyword to the value it had User response: Check the named profile keyword and
when creating the backup in order to perform a specific make appropriate adjustments.
operation.
BKI8352E Parameter parameter requires a decimal
BKI8344E Path path is listed more than once for value.
partitioning.
Explanation: The value specified for the named
Explanation: This is a DB2 – TSM interface problem. parameter does not comply with the defined range of
values.
System action:
System action:
User response: Contact your IBM support personnel.
User response: Check the named profile keyword and
make appropriate adjustments.

Chapter 2. Tivoli Storage Manager for ERP messages 35

BKI8353E • BKI8361E

BKI8353E Parameter parameter requires a value BKI8358E Parameter name requires 'ONLINE' or
greater than '0'. 'OFFLINE'.
Explanation: The value specified for the named Explanation: The parameter name only accepts the
parameter does not comply with the defined range of values ONLINE or OFFLINE.
values.
System action: Processing stops.
System action:
User response: Correct the value for the parameter
User response: Check the named profile keyword and specified in the profile.
make appropriate adjustments.
BKI8359E The profile parameter parameter has the
BKI8354E Parameter parameter requires 'NO' or wrong value 'value profile'. The expected
'YES'. value is 'value expected'.
Explanation: The value specified for the named Explanation: A profile parameter (or keyword) has a
parameter does not comply with the defined range of wrong value assigned. An alternate value is expected.
values.
System action:
System action:
User response: Check the named TSM for ERP profile
User response: Check the named profile keyword and keyword and make appropriate adjustments.
make appropriate adjustments.
BKI8360E Invalid keyword specified in the profile.
BKI8355E Parameter parameter requires 'ALL' or a
Explanation: The value specified for a keyword is
comma separated list of decimal values.
either wrong or is missing.
Explanation: The value specified for the named
System action:
parameter does not comply with the defined range of
values. User response: Check the named TSM for ERP profile
keyword and make appropriate adjustments.
System action:
User response: Check the profile keyword
BKI8361E Found files on the file systems to
DBPARTITIONNUM and make appropriate
backup for which backup was not
adjustments.
explicitly requested. Please provide a
negative list or clean your file systems.
BKI8356E product_name: interface problem in
Explanation: Although the previously mentioned files
function function: Invalid call sequence;
were not requested to be part of the backup, they will
the library was not initialized.
be copied because they reside on a file system that will
Explanation: An invalid internal call sequence was be backed up in its entirety. In order to allow backing
detected during execution of a dedicated function. up those files, they need to be added to a 'negative list'
or the checking for such files needs to be disabled.
System action:
Note that in case of a restore, these files would
User response: Check the logs for further information. typically be restored, even if this was not desired.
If the problem cannot be resolved contact your IBM
System action:
support personnel.
User response: Edit the 'CLIENT' section of the
profile. You can either set the parameter
BKI8357E product_name: interface problem in
'NEGATIVE_LIST' to 'NO_CHECK', to allow IBM Tivoli
function function: Invalid call sequence;
Storage FlashCopy Manager to back up any file stored
the operation was not initialized.
in a file system that will be backed up, or you can set
Explanation: An invalid internal call sequence was the parameter 'NEGATIVE_LIST' to point to a file (the
detected during execution of a dedicated function. 'negative list') that contains a list of all files and
directories that are allowed to be processed during
System action: backup. Any directory you add to the 'negative list' is
User response: Check the logs for further information. processed recursively. Note that there is only one
If the problem cannot be resolved contact your IBM 'negative list' for backup and restore. See FMM6969E
support personnel. for restore.

36 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8362E • BKI8371E

BKI8362E The trace parameters YES, NO, ON, and BKI8367E You cannot freeze the filesystem
OFF cannot be set in conjunction with without suspending or shutting down
other trace parameters. the database.
Explanation: The values YES, NO, ON and OFF in Explanation: Check the TSM for ERP profile keyword
conjunction with the TRACE keyword do not allow USE_AT and make appropriate adjustments.
further trace flags to be set. They are mutually
System action:
exclusive.
User response: Ensure either to suspend the database
System action:
or to bring the database offline and try to freeze the
User response: Check the TSM for ERP profile filesystem again.
keyword TRACE and make appropriate adjustments.
BKI8368E An invalid argument is specified for
BKI8363E The value value is not a valid trace flag. keyword keyword.
Explanation: The value specified for the TRACE Explanation: The specified argument could not be
keyword is invalid. converted into an equivalent integer value.
System action: System action:
User response: Check the TSM for ERP profile User response: Check the keyword argument and try
keyword TRACE and make appropriate adjustments. again. If the problem cannot be resolved contact your
IBM support personnel.
BKI8364E Error while parsing parameter
CONFIG_FILE. Directory 'directory' for BKI8369E Failed to execute program. Reason: reason.
node 'node' does not exist.
Explanation: The execution of program failed.
Explanation: The base directory containing the TSM
System action:
for ERP configuration file(s) for any participating DB2
partition does not exist or cannot be accessed. User response: Check the logs for further information.
If the problem cannot be resolved contact your IBM
System action:
support personnel.
User response: Ensure that the directory denoting the
base part of the CONFIG_FILE value (left part of the
BKI8370E The profile option
%DB2NODE substring) exists and has the right
TARGET_DATABASE_SUSPEND=
permissions.
OFFLINE is not allowed for an online
database backup.
BKI8365E The server stanza for LOG_SERVER
Explanation: A snapshot backup of a database that
'server' is missing.
was not suspended can only be done in offline mode.
Explanation: A TSM server stanza used by the
System action:
LOG_SERVER keyword is missing either in the option
file (dsm.opt) or in the system options file (dsm.sys). User response: Start the BRBACKUP utility with the
option '–t offline -d util_vol' and try again.
System action:
User response: Either the value of the LOG_SERVER
BKI8371E The profile parameter NEGATIVE_LIST
keyword in the TSM for ERP profile has to be adjusted
is not allowed. Use BR–TOOLS option
or an entry must be made or adjusted in the
"–n" to specify the negative list.
appropriate option file.
Explanation: The negative list value has to be
specified in the init<SID>.sap profile via the option
BKI8366E The values for parameter parameter are
'util_vol_nlist = (nfile_name1, nfile_name2, ...) |
expected to be in the range 0 to 6.
no_check'.
Explanation: The values of the keyword USE_AT have
System action:
to be in the range of 0 to 6.
User response: Adjust the init<SID>.sap profile
System action:
accordingly and try again.
User response: Check the TSM for ERP profile
keyword USE_AT and make appropriate adjustments.

Chapter 2. Tivoli Storage Manager for ERP messages 37

BKI8372E • BKI8380E

BKI8372E The profile option BKI8376E Verification of snapshot failed.

TARGET_DATABASE_SUSPEND=YES Reason:reason
requires a backup of type
Explanation: The snapshot backup could not be
volume_online. To solve this problem
verified successfully.
either the profile parameter
TARGET_DATABASE_SUSPEND can be System action:
set to OFFLINE or NO or the brbackup
backup device type should be set to User response: Check the logs for further information.
util_vol_online. Keep in mind, when If the problem cannot be resolved contact your IBM
you set the profile parameter support personnel.
TARGET_DATABASE_SUSPEND to
NO, the snapshot backup will be BKI8377E Function function does not support
mounted on a backup system to verify multiple backup ids within a single
its consistency. Make sure that a backup operation.
system is configured in that case.
Explanation: TSM for ACS was requested to perform
Explanation: A snapshot backup of a database that a volume function operation simultaneously for a set of
was suspended can only be done in online mode. objects that were backed up with multiple volume
System action: backup requests. This is currently not supported.

User response: Start the BRBACKUP utility with the System action:
option '–t online -d util_vol' and try again. User response: Use backups stored on the TSM server
to perform redirected restores or adjust the restore
BKI8373W The operation will execute the force command.
option (–F).
Explanation: Start the BRBACKUP utility with the BKI8378E Redirected restore of volume backups is
option '–t online -d util_vol' and try again. not supported yet.

System action: Explanation: TSM for ACS does not support restores
to an alternate data location. The restore always needs
User response: None. to be made to the original data location.
System action:
BKI8374W Operation will terminiate with error,
because backint was executed with User response: Use backups stored on the TSM server
verify option (–V). to perform redirected restores.

Explanation: The verify option simulates the

requested option and does not create a valid backup or BKI8379E Infile contains an invalid value: 'value'
restore. In order to prevent the calling process from Explanation: Each record of the infile has to start
regarding the current operation as successful, the verify either with the string '#NULL' or with the backup Id.
option will always yield a nonzero return code.
System action:
System action:
User response: Ensure each record of the infile
User response: Do not use the verify option if you satisfies the requirements. If the problem cannot be
want to create a backup or restore. resolved contact your IBM support personnel.

BKI8375E The value of the environment variable BKI8380E The profile option TSM_BACKUP=YES
ORACLE_SID is not allowed to have requires a snapshot backup of all
more than number digits. partitions of the database.
Explanation: The length of the ORACLE_SID value Explanation: The profile option TSM_BACKUP=YES
violates the defined range. implies offloading a snapshot backup to TSM. If this
System action: option is specified, all database partitions have to be
part of the snapshot backup.
User response: Check the current value of
ORACLE_SID and if necessary, correct it according to System action:
the allowed length. Try again. User response: Specify the 'ALL
DBPARTITIONNUMS' clause as part of the DB2 backup
command and try again.

38 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8381W • BKI8387W

required in order to properly adjust the profile.

BKI8381W The following error occured while
verifying the configuration for server System action:
'server_name' in the profile:
User response: Provide the application type when
Explanation: The profile section for server server_name invoking the wizard with options 'acsd –f wizard –m
is not correct. The actual error is following this <application type>'. The preferred method, however, is
message. to call the setup script without options.
System action:
BKI8385E In order to create a new profile the
User response: Adjust the profile and correct the error
wizard needs to be invoked with option
following this message.
–m <application type>.
Explanation: 'acsd –f wizard' was invoked to create a
BKI8382E The previous error(s) can be prevented
new profile. In this case it is required to specify the
by executing restore with negative list
application type with option –m.
set to 'no_check'.
System action:
Explanation: An error occurred while inspecting file
systems for files that should be excluded during the User response: Provide the application type when
backup/restore operation. This error precedes the invoking the wizard by using the options 'acsd –f
current message. Note that the file system inspection wizard –m <application type>'. Alternatively, you can
can be turned off by setting the parameter use the database–specific version of the setup script
'NEGATIVE_LIST' to 'NO_CHECK'. (setup_<database>.sh) to create a new profile and
configure TSM for ACS.
System action:
User response: Resolve the root cause for this problem
BKI8386E Parameter parameter name requires a
(previous error) or change the value of the parameter
decimal value of 0 or greater.
'NEGATIVE_LIST' to 'NO_CHECK'. Depending on the
application type, this can be accomplished by v (for Explanation: The value specified for the named
DB2 and native Oracle) editing the TSM ACS profile parameter does not comply with the defined range of
and set the parameter 'NEGATIVE_LIST' to 'no_check' v values.
(for SAP(R) for Oracle) editing the BR*Tools profile
*.sap and set the parameter 'util_vol_nlist' to 'no_check' System action:
Note that changing 'NEGATIVE_LIST' to 'NO_CHECK' User response: Check the named profile keyword and
implies that TSM for ACS would potentially backup all make appropriate adjustments.
files residing on the requested file systems. This true
even if they were not explicitly requested and resided
on the requested file systems, and even if they were not BKI8387W The following extra files are found in
explicitly requested during the backup. At restore time the directories to be backed up: 'filename'
all of these objects would typically be restored. Explanation: The extra files were not requested to be
part of the backup. The files may be copied if they are
BKI8383E BR–Tools are required to set the located in a file system that is to be backed up in its
environment variable BI_RUN for entirety. If the files are in a file system that does not
volume backups. participate in the backup they are not copied.

Explanation: This is a unique ID from a BR*Tools run System action:

(normally it is the name of the BR*Tools log). If this User response: To avoid generating this message, edit
variable is set then BACKINT recognizes that a call the 'CLIENT' section of the profile. You can set the
from BR*Tools 7.10 or higher was triggered. parameter 'NEGATIVE_LIST' to 'NO_CHECK'. Then,
System action: IBM Tivoli Storage FlashCopy Manager backs up any
file that is stored in a file system participating in the
User response: Ensure that BR*Tools 7.10 or later is backup. Alternatively, you can set the
used and rerun the operation. 'NEGATIVE_LIST' parameter to point to a file
('negative list') containing a list of all files and
BKI8384E Failed to determine the directories that are allowed to be processed during the
APPLICATION_TYPE of the profile. backup. Any directory that you add to the 'negative
Please invoke wizard with option –m list' file is processed recursively. Note there can be only
<application type>. one 'negative list' file for both backup and restore
operations.
Explanation: 'acsd –f wizard' was invoked to modify
an existing profile, and the APPLICATION_TYPE could To avoid false warnings for files in the nested file
not be identified by inspecting this profile. This is systems that do not participate in the backup, add the

Chapter 2. Tivoli Storage Manager for ERP messages 39

BKI8388W • BKI8395E

mount points of the nested file systems to the 'negative volume groups) to verify the database files because the
list' file. file systems are not mounted and/or the volume
groups are not imported.
To avoid false warnings for files or directories that are
pointed to by symbolic links and that do not participate System action:
in the backup, add the file system mount points of
User response: There are two options to solve this
these files to the 'negative list' file.
problem: 1. Import all volume groups and mount all
Note: FlashCopy Manager does not automatically file systems that contain database files. 2. If the first
include nested file systems and files pointed to by option is not possible as a consequence of a disaster or
symbolic links in the FlashCopy backup operation. a failing previous restore operation, the negative list
check cannot be performed at all and must be switched
to 'no_check'. Depending on the application type, this
BKI8388W Additional files to restore were
can be accomplished by v (for DB2 and native Oracle)
discovered on the file systems: 'file list'
editing the TSM ACS profile and set the parameter
Explanation: A FlashCopy restore operation is 'NEGATIVE_LIST' to 'no_check' v (for SAP(R) for
performed with the profile parameter NEGATIVE_LIST Oracle) editing the BR*Tools profile *.sap and set the
set to WARN. This operation replaces complete file parameter 'util_vol_nlist' to 'no_check' Note that
systems with the content of the file systems at the time changing NEGATIVE_LIST to NO_CHECK implies that
of backup. Each file that currently resides on the file TSM for ACS would potentially backup all files
systems to be restored (but were not part of the residing on the requested file systems. This true even if
original backup) will be listed. they were not explicitly requested and resided on the
requested file systems, and even if they were not
System action: Processing continues. explicitly requested during the backup. At restore time
User response: None. all of these objects would typically be restored.

BKI8389W The following volume groups / file BKI8393E The keyword TARGET_SET requires a
systems are currently not accessible: target set name as argument.
volumegroups/filesystems Explanation: The keyword TARGET_SET specified
Explanation: The listed volume groups or file systems within the target set definition file needs to be followed
are not accessible. TSM ACS tries to verify that only by an argument defining the unique name of the target
database files reside in the volume groups or file set.
systems that will be restored. But it was encountered System action: Please have a look into your target set
that it was not possible to access the file systems (in the file (.fct) and correct the entry accordingly.
volume groups) to verify the database files because the
file systems are not mounted or the volume groups are User response:
not imported, or both. This warning message is
followed by message BKI9390E which gives more
BKI8394E Error while parsing TARGET_SET target
information.
set name: Illegal number of arguments.
System action:
Explanation: The keyword TARGET_SET specified
User response: This is just a warning message. Follow within the target set definition file needs to be followed
the instructions of the user response of BKI8390E. by exactly one argument defining the unique name of
the target set. No additional arguments are allowed.

BKI8390E Failed to validate that only database System action:

files will be overwritten during restore,
User response: Please have a look into your target set
because some of the database
file (.fct) and correct the entry accordingly.
filesystems are currently not accessible.
Please import volume groups and/or
mount all filesystems and restart the BKI8395E Error while parsing TARGET_SET target
restore. If you cannot mount the set name in volumes file: A multi
filesystems as a consequence of a partition backup requires the use of the
disaster or a failing previous restore keyword PARTITION in the target set
operation, this error can be prevented section.
by executing restore with negative list
Explanation: On a partitioned DB2 environment, the
set to 'no_check'.
TARGET_VOLUME entries within the target set
Explanation: TSM ACS tries to verify that only definition file need to be enclosed by nested
database files reside in the volume groups / file 'PARTITION' sections to determine for which partition
systems that will be restored. But it was encountered this target volume(s) apply.
that it was not possible to access the file systems (in the

40 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8396E • BKI8403E

System action:
BKI8399E The mode mode of parameter parameter is
User response: Modify your target set definition file only supported for device_type .
accordingly. Example: >>> TARGET_SET SET_1 >>>
Explanation: The requested mode mode is only
PARTITION NODE0000 TARGET_VOLUME 40913158 -
supported for device_type.
- TARGET_VOLUME 40A13158 - - <<< >>>
PARTITION NODE0001 TARGET_VOLUME 40B13158 - System action:
- TARGET_VOLUME 50913158 - - <<< <<<
User response: Choose a supported mode..

BKI8396E Error while parsing TARGET_SET target

BKI8400E Error while parsing statement 'device
set name in volumes file: It is not
class' in profile. The statement partition
allowed to specify a portion of a target
number is required to be a number.
set without keyword PARTITION, if
this keyword is used for other portitions Explanation: The optional condition
in the same target set definition. 'ON_PARTITIONN' of the profile parameter
'DEVICE_CLASS' needs to be followed by an integer
Explanation: On a partitioned DB2 environment, the
number.
TARGET_VOLUME entries within the target set
definition file need to be enclosed by nested System action:
'PARTITION' sections to determine for which partition
this target volume(s) apply. As soon as embedded User response: Please check your profile and correct
PARTITION subsections are used this means that ALL the 'ON_PARTITIONN' entries accordingly.
TARGET_VOLUME entries need to be enclosed in
PARTITION subsections. BKI8401E DEVICE_CLASS device class was
System action: encountered multiple times within a
single DEVICE_CLASS statement.
User response: Correct your target set definition file
accordingly. Explanation: The parameter 'DEVICE_CLASS' of the
'CLIENT' section allows to enlist multiple device classes
which are then applied in a round robin process.
BKI8397E Error while parsing TARGET_SET target However, each enlisted device class must not occur
set name in volumes file: the parameter multiple times within the same enumeration.
PARTITION requires exactly one
parameter. System action:

Explanation: On a partitioned DB2 environment, the User response: Please check your profile and correct
TARGET_VOLUME entries within the target set the 'DEVICE_CLASS' entries accordingly.
definition file need to be enclosed by nested
'PARTITION' sections. The keyword 'PARTITION' BKI8402E No DEVICE_CLASS found that can be
needs to be followed by the unique name of the used for the current operation.
partition.
Explanation: The application of a 'DEVICE_CLASS'
System action: entry within the 'CLIENT' section of the profile can be
User response: Check whether all PARTITION restricted by a number of optional conditions, e.g. by
subsections within your target set definition file have a time frame of DB2 partition number. If this error occurs
unqiue partition name and correct the entries if none of the DEVICE_CLASS entries within the profile
necessary. matches the conditions currently given (current time,
given partition, given weekday).

BKI8398E Error while parsing statement 'parameter System action:

name' in profile. The statement 'from or User response: Check the conditions specified for the
to' is required to be in the form hh:mm. 'DEVICE_CLASS' entries within your profile. It needs
Explanation: The optional conditions 'FROM' and 'TO' to be ensured that exactly one entry matches any
of the profile parameter 'parameter name' need to be imaginable condition at any time.
followed by a time in the format 'hh:mm'.
System action: BKI8403E The keyword keyword was found
multiple times without qualifier qualifier.
User response: Please check your profile and correct
the times accordingly. Explanation: If the parameter keyword is specified
without additional qualifiers it is representing the
global default. This global default can be defined only
once. All other entries of parameter keyword need to be

Chapter 2. Tivoli Storage Manager for ERP messages 41

BKI8404E • BKI8435W

restricted by additional conditions.

BKI8408E The parameter parameter is not allowed
System action: as a name for a target set.

User response: Please check your profile. The Explanation: One possible distinctness of the
parameter keyword must not occur multiple times parameter 'TARGET_SET' is to specify target set
without additional conditions. definitions via a naming convention instead of a target
set definition file (for SVC only). The argument
parameter does not meet these naming conventions.
BKI8404E The following statement contains
incompatible options statement. System action:

Explanation: The parameter statement within the User response: Please check the arguments of the
'CLIENT' section of the profile is followed by parameter 'TARGET_SET' within your profile and
additional options which are contradictory to each correct them accordingly.
other.
System action: BKI8409E The parameter TARGET_NAMING is
required to contain the wildcards source
User response: Please check the parameter statement and targetset.
within your profile. For example, it is not possible to
combine the options 'MANDATE' and 'TSM_ONLY'. Explanation: The parameter 'TARGET_NAMING'
needs to follow particular conventions including the
wildcards source and targetset to be valid.
BKI8405E The following statement is missing
mandatory options statement. System action:

Explanation: The parameter statement within the User response: Please check the arguments of the
'CLIENT' section of the profile must be followed by an parameter 'TARGET_NAMING' within your profile and
option defining the mode of how offline backups are correct them accordingly.
handled.
System action: BKI8414E Error while parsing profile profile:
Delimiter 'delimiter' missing.
User response: Please check the parameter statement
within your profile. It needs to include either 'NO', Explanation: A syntax error has been detected within
'YES', 'MANDATE', or 'TSM_ONLY' as an option. you profile.
System action:
BKI8406E There are two object type associated with
User response: Please check the syntax and format of
partition partition name.
your profile.
Explanation: The profile associates the same partition
with multiple objects of object type. The name of the
BKI8420E Full file-based backups into the
partition and of the object type are identified in this
repository are not allowed when
message.
'ALLOW_FULL_FILE_BACKUP' is set to
System action: The operation fails. 'NO'.

User response: Update the profile so that each Explanation: If you want to use 'FlashcopyManager' to
partition is listed as a member of only one object of perform a backup with options util_file or
object type. util_file_online, set the option
ALLOW_FULL_FILE_BACKUP to YES in the profile.

BKI8407E An illegal partition number has been System action:

specified for parameter candidate name.
User response: Correct the setting for the parameter
Explanation: The parameter parameter expects integer within your profile. You can also change backup
partition numbers as argument. options.

System action:
BKI8435W Annotation file 'file' could not be loaded.
User response: Please check the parameter parameter
within your profile and correct it accordingly. Explanation: The annotation file is required by the
profile wizard for displaying more expressive prompts
and online help. However, if this file is missing the
wizard is still operational.
System action:

42 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8436W • BKI8514W

User response: The annotation file is integral part of

BKI8465E The value value for parameter parameter
the product. If it is missing this means your product
is out of valid range (min - max).
installation is corrupt. Please perform a reinstallation. If
the warning message still occures please contact your Explanation: The value specified for the named
support line. parameter does not comply with the defined range of
values.
BKI8436W Problems occured on final validation of System action:
profile. Incorrect parameters have been
User response: Check the named profile keyword and
marked in the written profile. Please
make appropriate adjustments.
check.
Explanation: Profile parameters for that a user-defined
BKI8511I The command is: command name
value is obligatory have been skipped without
specifying a value. Explanation: This is an information message echoing
the command.
System action:
System action:
User response: Please rerun the profile wizard for the
given profile and ensure you specify a valid value for User response: None.
each parameter marked with *input mandatory*.

BKI8512I Return code is: return code

BKI8437I Verifying password...
Explanation: This message shows the return code of
Explanation: After a password has been entered the the Backup Object Manager. Valid return codes: 0 The
wizard is verifying it by performing a test connection requested action was performed successfully. 1 The
to the according entity. requested action was performed successfully; however,
some warnings were issued. 2 or greater The requested
System action:
action could not be performed due to errors. In this
User response: Wait for outcome of the verification. If case, an error message should be logged, too.
the verification is successfull the wizard proceeds with
System action:
the next password or writes the password files. If the
verification fails the user is asked whether he wants to User response: None if the return code is 0. If the
retry or ignore the issue. return code is greater than 0, analyze the error and/or
warning messages. Resolve errors before starting the
action again.
BKI8439E Could not read password filename from
profile 'profile'. File does not exist.
(Check options -p, -b) BKI8513W 'TDP_DIR' is not set. The temporary
path will be used.
Explanation: If the filename for the password file is
not explicitly specified by the option '-b' the wizard Explanation: The environment variable 'TDP_DIR' is
tries to read this information from the profile. The not set and therefore, the log will be written to the
profile being consulted is either the default profile system's temporary path instead.
'profile' or the profile specified by option '-p'. If this
error occurs there is either no default profile available System action:
or the profile specified by option '-p' does not exist. User response: Set the 'TDP_DIR' environment
System action: variable.

User response: Check options '-p' and '-b'.

BKI8514W 'TDP_DIR' is not set correctly. The
temporary path will be used.
BKI8441E Please specify either only backup id's or
only backup id's with files. Explanation: The variable TDP_DIR is set but contains
an invalid path. All run logs will be written to the
Explanation: You specified some backup id's with files machines temporary directory instead.
and some backup id's without files.
System action:
System action:
User response: Check and reset the environment
User response: Please specify either only backup id's variable TDP_DIR.
or only backup id's with files.

Chapter 2. Tivoli Storage Manager for ERP messages 43

BKI8520E • BKI8530E

BKI8520E No command was specified. BKI8526E The DB2 database alias can consist of at
most characters characters.
Explanation: backom was called without a command
line. Explanation: The name given for the DB2 alias does
not comply with the DB2 naming conventions.
System action:
System action:
User response: Check the command syntax and
correct the call. User response: Correct the DB2 alias name.

BKI8521E Command option 'command option' BKI8527E Invalid node. Specify it in the format
requires an argument. node format.
Explanation: A command option requiring an Explanation: The name given for the DB2 node does
argument was specified without an argument. not comply with the DB2 naming conventions. Node
numbers must be specified in the displayed format, for
System action: Check the command syntax and
example 'NODE0000' or '0000'.
correct the call.
System action:
User response:
User response: Correct the DB2 node number.
BKI8522E Invalid command 'command'.
BKI8528E Invalid timestamp. Specify the format as
Explanation: backom was called with an invalid
'yyyymmddhhmmss', wildcards '*' or '?'
command.
are permitted.
System action:
Explanation: Specify digits in the format
User response: Check the command syntax and 'yyyymmddhhmmss' or mixed with wildcards '*' or '?'.
correct the call. where: v yyyy is the year, specified as four digits, v mm
is the month, specified as two digits, with leading zero
for the months January to September, v dd is the day of
BKI8523E Error during action. the month, specified as two digits, with leading zero
Explanation: An error occurred while performing the for days 1 to 9, v hh is the hour of the day, 00 to 23,
named action. with leading zero for hours 0 to 9, v mm is the minutes
of the hour, 00 to 59, with leading zero for minutes 0 to
System action: 9, v ss is the second of the minute, 00, to 59, with
User response: Look for other error messages in order leading zero for seconds 0 to 9. Any digits can be
to analyze the problem. replaced by wildcards '*' or '?', where v * means any
number of any digits, v ? means exactly one digit of
any value.
BKI8524E An online restore of the Tablespace is
not allowed. System action:

Explanation: Either the database setup or the kind of User response: Correct the timestamp.
backup prevents an online table space backup.
System action: BKI8529E Invalid log sequence number. Specify it
in the format log sequence format.
User response: If you need to do a table space restore
it must be done offline. Explanation: The information on the log sequence
number(s) does not comply with the expected format.
Accepted log sequence numbers are for example '123'
BKI8525E The DB2 instance name can consist of at or 'S0000123.LOG'.
most characters characters.
System action:
Explanation: The name given for the DB2 instance
does not comply with the DB2 naming conventions. User response: Correct the log sequence number(s).

System action:
BKI8530E Profile 'file name' does not exist or cannot
User response: Correct the DB2 instance name. be accessed.
Explanation: Either an existing file could not be
opened, or a file could not be created.
System action:

44 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8531E • BKI8542E

User response: Check the attributes of the file and/or User response: Correct the output mode command
its directory. For backup processing, read access is option.
required for the files to be backed up. For restore
processing, write access is required for the target
BKI8536E Wildcard characters are not allowed for
location of the files to be restored.
command 'command'.
Explanation: For the BackOM commands 'restore
BKI8531E Directory 'file path' does not exist or
database', 'restore tablespace', 'restore tablespace online'
cannot be accessed.
and 'restore DB2 history file' it's not allowed to specify
Explanation: A file path cannot be accessed. the wildcard characters '*' and '?' in a timestamp
command option.
System action:
System action:
User response: Check the attributes of the file and/or
its directory. For backup processing, read access is User response: Correct the timestamp command
required for the files to be backed up. For restore option.
processing, write access is required for the target
location of the files to be restored.
BKI8537E The path 'path' is not absolute.
Explanation: A command line argument requires a
BKI8532E Invalid log chain number. Specify it in
fully qualified path which was not given.
the format log chain format.
System action:
Explanation: The information on the log chain
number(s) does not comply with the expected format. User response: Specify the fully qualified path.
Accepted log chain number(s) are for example '123' or
'C0000123'.file path .
BKI8538E The Tablespace Definition Information
System action: 'file name' cannot be processed.
User response: Correct the log chain number(s). Explanation: The TDI file could not be parsed because
of errors. There are more specific parser error messages
before this message occurs.
BKI8533E A timestamp range is not allowed for
command 'command'. System action:
Explanation: A timestamp range is not allowed for User response: Check for and respond to preceding
command restore database, restore tablespace, restore error messages in the Backup Object Manager log.
tablespace online and restore DB2 history file. Only a
single timestamp argument can be used.
BKI8540I Using component_name at host name:port
System action:
Explanation: The component_name service named is
User response: Correct the timestamp command used for the current action.
option.
System action:

BKI8534E Command option 'command option' is User response: None.

missing.
Explanation: A command was issued without BKI8541I Using profile 'profile path'.
specifying a required command option. Explanation: The profile named is used for the current
System action: Check the command syntax and action.
correct the call. System action:
User response: Check the command syntax and User response: None.
correct the call.

BKI8542E Profile 'profile path' cannot be read.

BKI8535E Invalid output mode. Specify one of the
keywords keyword list. Explanation: The Backup Object Manager tried to use
the profile named but the profile was not available or
Explanation: Only the listed keyword values are could not be read. The location of the profile is
allowed with the output mode command option –m. specified via command line as argument to option '–e'
System action: or in environment variable 'XINT_PROFILE'.
System action:

Chapter 2. Tivoli Storage Manager for ERP messages 45

BKI8543I • BKI8557E

User response: Make sure that the profile is available

BKI8550W Environment variable 'environment
at the location specified in option '–e' on the command
variable' for output mode has wrong
line or in environment variable 'XINT_PROFILE'. Check
value. Using default.
the attributes of the profile and the corresponding
directory and make sure that the file can be accessed. Explanation: The default output mode can be
overridden by the named environment variable.
Accepted values are "short", "normal", or "detailed".
BKI8543I Querying TSM for file(s) 'file list'.
The system default is "short" for actions on DB2 log
Explanation: The Backup Object Manager checks if the files, "normal" otherwise.
files listed are available on the TSM server(s) specified
System action:
in the corresponding profile.
User response: Specify an appropriate value for the
System action:
environment variable named, or remove the
User response: None. environment variable.

BKI8545I No image type image(s) found. BKI8551E Not all data written to 'file path'.

Explanation: A request could not be satisfied because Explanation: Restoring raw or DB2 log file data ended
the files to be processed are not available on the TSM before all data retrieved from TSM could be written to
server. the file named. The file is incomplete. named.

System action: System action:

User response: Check if the file(s) were specified User response: Make sure there is sufficient space for
correctly in the request. the data to be restored.

BKI8546E Environment variable 'environment BKI8552E File 'file path' could not be closed.
variable' is not set or not set correctly.
Explanation: After restoring raw or DB2 log file data,
Explanation: A required environment variable is not the target file could not be closed.
set at all or has a value that is not allowed.
System action:
System action:
User response: Retry the action.
User response: Check the documentation for the
appropriate values of the environment variable named
BKI8555E Variable 'DB2DBDFT' or command
and set its value accordingly.
option 'alias' is required.
Explanation: The password command needs the
BKI8548I Elapsed time: time value
name/alias of the database, for which the Data
Explanation: After restore and delete, the time elapsed Protection for SAP configuration file has to be adapted.
during the action is displayed.
System action:
System action:
User response: Either set the environment variable
User response: None. DB2DBDFT or provide the command option 'alias' with
the password command and try again.

BKI8549E Unable to create file 'file name'.

BKI8556E Unable to get hostname.
Explanation: During restore, the file to be restored
cannot be created in the target location. Explanation: The machines hostname could not be
determined.
System action:
System action:
User response: Check if there is sufficient space
available for the file to be restored. Check the attributes User response: Check the TCP/IP configuration of the
of the target directory; write access is required. If the machine.
target file already exists, check that write access is
granted
BKI8557E The config file 'initfile name.bki' could
not be created.
Explanation: Data Protection for SAP tries to create
the configuration file named if it is not present at the
location specified by the Data Protection for SAP profile

46 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8558I • BKI8586I

keyword CONFIG_FILE. However, the file cannot be

BKI8561W Database 'alias' not listed in the system
created. This may either be caused by an incorrect path
database directory.
specified by keyword CONFIG_FILE, or the user may
not have the appropriate permissions for creating the Explanation: The database alias does not exist. Because
file. there is a dependency between the alias and the
settings for Data Protection for SAP there might be
System action:
problems during database backup or restore runs.
User response: Make sure the path specified by Nevertheless, the Data Protection for SAP configuration
keyword CONFIG_FILE is correct and the permissions file (initalias.utl) will be created and adapted.
are set appropriately.
System action:
User response: Check if the alias specified does match
BKI8558I Setting TSM password for partition
to an entry in the DB2 system database directory.
'partition number' on host 'host name'.
Further, check the argument for the Data Protection for
Explanation: The Data Protection for SAP TSM SAP profile keyword CONFIG_FILE and if necessary
password is set on the host named for the DB2 adapt it appropriately.
partition indicated.
System action: BKI8583E Multiple possible values for parameter
'INCREMENTAL_LEVEL'
User response: None. detected:ambigous statements
Explanation: Multiple specifications of the parameter
BKI8559W For partition 'partition number' switch to 'INCREMENTAL_LEVEL' with overlapping time spans
host 'host name' and issue the command have been detected in the profile.
again.
System action: Processing stops.
Explanation: When verifying the TSM password, the
Data Protection for SAP configuration file is modified. User response: The parameter
If the Data Protection for SAP profile keyword 'INCREMENTAL_LEVEL' can be specified multiple
CONFIG_FILE points to an NFS mounted (UNIX or times within the profile to use different values at
Linux) or a shared (Windows) path accessible to all different days of the week or different times during the
hosts in a DB2 ESE (EEE) environment, for example the day. But these multiple definitions must not overlap.
instance home, all configuration files of the various Correct the time specifications. Try the operation again.
partitions can be modified simultaneously. If, in
contrast, keyword CONFIG_FILE points to a local path,
BKI8584I Delete command completed successfully.
only the configuration files of the local partitions can
be modified. In this case, the password verification Explanation: The object(s) specified with the delete
needs to be done from each host. The message indicates command were successfully deleted from the TSM
the partitions whose associated configuration files are server.
not accessible. In order to avoid this administrative
System action:
overhead, it is recommended to place the Data
Protection for SAP configuration files in a file system User response: None.
shared by all hosts hosting a partition of the database.
System action: BKI8585W Delete command completed successfully,
but had warning(s).
User response: Make sure to verify the TSM
password(s) for all partitions of the database. Explanation: The object(s) specified with the delete
command were deleted with warning(s) from the TSM
server.
BKI8560E Partition 'partition number' not found in
the database configuration. System action:
Explanation: The DB2 partition specified could not be User response: Check the Backup Object Manager log
found in the database configuration. file for further detailed messages and if required, do
the requested interventions manually.
System action:
User response: Check the configuration of the DB2
BKI8586I Delete command was aborted.
ESE(EEE) environment (db2nodes.cfg, environment
variable DB2NODE) and try again. Explanation: The delete command was aborted by the
user. No object(s) were deleted from the TSM server.
System action:

Chapter 2. Tivoli Storage Manager for ERP messages 47

BKI8587E • BKI8619E

User response: None.

BKI8613E Terminating restore ...
Explanation: An error occurred, and the database
BKI8587E Delete command failed due to an error.
restore terminates.
Explanation: The delete command failed during
System action:
execution. Not all objects were deleted from the TSM
server. User response: Check for and respond to preceding
error messages in the Backup Object Manager and the
System action:
shared library run logs. Additional information may be
User response: Check the Backup Object Manager log found in the DB2 diagnostic log (db2diag.log).
file for further detailed messages and try to resolve the
error which led to the delete failure. Retry the action. If
BKI8615I Restore command completed
the error still exists, contact the IBM Support.
successfully.
Explanation: The object(s) specified with the restore
BKI8588E Delete command has not been started or
command were successfully restored from the TSM
no delete result information is available.
server.
Explanation: This message indicates that an operation
System action:
did not complete successfully. Typically, some other
error condition was detected before. User response: None.
System action:
BKI8616W Restore command completed
User response: Contact the IBM Support.
successfully with warnings.
Explanation: The object(s) specified with the restore
BKI8589E Query command failed due to an error.
command were restored with warning(s) from the TSM
Explanation: The query command failed during server.
execution. Not all queried objects can be displayed.
System action:
System action:
User response: Check the Backup Object Manager log
User response: Check for and respond to preceding file for further detailed messages and if required, do
error messages in the Backup Object Manager log. In the requested interventions manually.
the absence of preceding error messages, contact IBM
Support.
BKI8617I Restore command was aborted.
Explanation: The restore command was aborted by
BKI8610I Restoring type ...
the user. No object(s) were restored from the TSM
Explanation: The restore of type has started. server.

System action: System action:

User response: None. User response: None.

BKI8611I Do you want to overwrite the existing BKI8618E Restore command failed due to an error.
database (y/n)?
Explanation: The restore command failed during
Explanation: execution. Not all objects were restored from the TSM
server.
System action:
System action:
User response:
User response: Check the Backup Object Manager log
file for further detailed messages and try to resolve the
BKI8612I Continuing restore ... error which led to the restore failure. Retry the action.
Explanation: The database restore continues. If the error still exists, contact the IBM Support.

System action:
BKI8619E Restore command has not been started
User response: None. or no restore result information is
available.
Explanation: This message indicates that an operation
did not complete successfully. Typically, some other

48 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8621I • BKI8637I

error condition was detected before.

BKI8631I Backup command completed
System action: successfully.

User response: Check for and respond to preceding Explanation: The backup operation completed
error messages in the Backup Object Manager log. successfully; the backup image can be used for
restoring. In the case of a full database backup, the TDI
image was generated and stored to TSM, too.
BKI8621I Restoring file 'file name' ...
System action:
Explanation: The system started restoring the file
indicated. User response: None.

System action:
BKI8632W Backup command completed
User response: None. successfully with warnings.
Explanation: The backup operation completed
BKI8622I Deleting type ... successfully; the backup image can be used for
Explanation: The deletion of type has started. restoring. However, some problems occurred.

System action: System action:

User response: None. User response: Check the warning messages and take
corrective actions if necessary.

BKI8623I Deleting file 'file name' ...

BKI8634E Backup command failed due to an error.
Explanation: The system started deleting the file
indicated. Explanation: No backup was made due to previous
errors.
System action:
System action:
User response: None.
User response: Check for and respond to preceding
error messages in the Backup Object Manager log.
BKI8626W The Tablespace Definition Information
'file name' could not be deleted.
BKI8635E The command option 'option' must be a
Explanation: The system tried to remove the TDI floating point number.
image from TSM, but did not succeed.
Explanation: An invalid argument was specified for
System action: command option option.
User response: Try to remove the image manually System action:
using the Backup Object Manager raw delete facility.
User response: Correct the command syntax.

BKI8629E The 'variable name' environment variable

is not set. BKI8636E The command option 'option' must be
one of values.
Explanation: The specified environment variable is not
set, processing cannot continue for the requested Explanation: An invalid argument was specified for
operation. command option option.

System action: Processing ends. System action:

User response: Ensure that when you run the product User response: Correct the command syntax.
that you use the correct user ID so that the
environment variable is set. BKI8637I Type state backup of 'alias' started ...
Explanation: A backup operation of database alias of
BKI8630E The command option 'option' must be a type type has started.
number.
System action:
Explanation: An invalid argument was specified for
command option option. User response: None.
System action:
User response: Correct the command syntax.

Chapter 2. Tivoli Storage Manager for ERP messages 49

BKI8638I • BKI8651W

without including DB2 log files.

BKI8638I Type state backup of tablespace(s)
tablespace#1,...,tablespace#n of 'alias' started System action:
...
User response: Make sure to backup DB2 log files
Explanation: A backup operation of table space(s) separately.
tablespace#1 ... tablespace#n of database alias of type type
was started.
BKI8648I number of files in this run file(s) were
System action: Processing continues. stored successfully in this run on the
'hostname' node. A total number of stored
User response: None.
number of files totally files out of total
number of files files are stored in the data
BKI8639I Including log files in backup image ... backup that is identified by the external
'backup id' backup ID.
Explanation: The DB2 log files are stored as part of
the backup image. Explanation: This is a progress message.
System action: System action: Processing continues.
User response: None. User response: N/A

BKI8640I Using number buffers with a size of size BKI8649E The automatic deletion of backups is
... not supported. Change the value of the
parameter name parameter to 0.
Explanation: For backup or restore operations, the
indicated number of buffers of the size displayed are Explanation: The automatic deletion of backups is not
used. supported.
System action: System action: Processing ends.
User response: None. User response: Ensure that the value of the specified
parameter is set to 0. As a consequence, backups are
not automatically deleted.
BKI8641I Using number session(s) ...
Explanation: For backup or restore operations, the
BKI8650E To restore from all found_copies detected
indicated number of TSM sessions is used.
redo log copies, required_sessions sessions
System action: must be opened. But currently only
configured_sessions are allowed.
User response: None.
Explanation: For the object that should be restored
overall found_copies copies have been found on the
BKI8642I Using a degree of parallelism of number Tivoli Storage Manager server. To allow transparent
... failover to other copies in case of errors Data Protection
Explanation: For backup or restore operations, the for SAP must be able to open required_sessions sessions.
degree of parallelism is displayed. But the current configuration allows to open only
configured_sessions sessions.
System action:
System action: Processing ends.
User response: None.
User response: Check the profile parameter
MAX_RESTORE_SESSIONS or if not set check the
BKI8643I Using vendor library at 'lib path' ... value of parameter MAX_SESSIONS. Increase the value
Explanation: For backup or restore operations, the to be at least as large as found_copies. Ensure the overall
named vendor library is used. number of sessions that are configured over all server
stanzas in the Data Protection for SAP profile is at least
System action: as large as found_copies.
User response: None.
BKI8651W Your version of DB2 does not support
BKI8644W Offline backups cannot include log including log files. The option –L is
files. The option –L is being ignored. being ignored.

Explanation: An offline backup operation was started, Explanation: A backup was started, requesting the
requesting the DB2 log files to be included. This is not DB2 log files to be included, but your version of DB2
possible with an offline backup. The backup is done does not support this feature. For including DB2 log

50 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8652I • BKI8661W

files in the backup image, DB2 V.8.2 or later is required.

BKI8657W Number is not a valid partition number
System action: for a non–partitioned database.
Assuming partition 0.
User response: Make sure to backup DB2 log files
separately. Explanation: The partition number specified in the
call to Backup Object Manager does not denote a valid
partition of the database. Therefore, the default
BKI8652I DB2 version 'version' with number bits partition 0 will be used by DB2 and by Backup Object
detected. Manager.
Explanation: The indicated DB2 version was detected System action:
by Backup Object Manager.
User response: If your database is not partitioned do
System action: not specify the partition number for further actions.
User response: None.
BKI8658E Number is not a partition number of the
BKI8653I Using autonomic buffer size and database or does not denote a partition
number of buffers ... on this host.

Explanation: The buffer size and the number of Explanation: The partition number specified does not
buffers used for backup or restore is automatically denote a valid database partition or is not the partition
determined by DB2. located on the system where Backup Object Manager is
called. Backup Object Manager can only operate on
System action: partitions residing on the same host.
User response: None. System action:
User response: Either change number to a partition
BKI8654I Using an autonomic buffer size with number of a local partition, or start Backup Object
number buffers ... Manager from the same host where the partition
Explanation: The buffer size used for backup and resides.
restore is automatically determined by DB2. The
number of buffers to be used was specified in the call BKI8659I Creating tablespace definition
to the Backup Object Manager. information ...
System action: Explanation: The table space definition information
User response: None. (TDI) is being created in memory.
System action:
BKI8655I Using an autonomic number of buffers User response: None.
with a size of size ...
Explanation: The number of buffers to be used for BKI8660I Saving tablespace definition
backup and restore are determined by DB2. The buffer information ...
size to be used was specified in the call to the Backup
Object Manager. Explanation: The table space definition information
(TDI) is being stored on the TSM server.
System action:
System action:
User response: None.
User response: None.

BKI8656I Using an autonomic degree of

parallelism ... BKI8661W Could not create Tablespace Definition
Information.
Explanation: The number of DB2 processes (UNIX or
Linux) or threads (Windows) used for reading or Explanation: The system could not collect the table
writing data from/to table space containers during space definition information. The backup was made
backup and restore is determined by DB2. without TDI. As a result, the backup can be used for
restoring the system, but it cannot be used for restoring
System action: to a different location.
User response: None. System action:
User response: Ensure that your database is enabled
to accept CLI connections.

Chapter 2. Tivoli Storage Manager for ERP messages 51

BKI8662W • BKI8670I

BKI8662W Could not save Tablespace Definition BKI8667W Tablespace tablespace with ID id was not
Information. redirected because its container on
source system SID is not located in a
Explanation: The system could not save the TDI on
path starting with 'path'.
TSM. The backup was made without TDI. As a result,
the backup can be used for restoring the system, but it Explanation: The named table space of type SMS was
cannot be used for restoring to a different location. not redirected because the definition of the table space
container in the source system does not match the
System action:
database characteristics that Backup Object Manager
User response: Check for and respond to preceding expects and that are cited in the message. Therefore,
error messages in the Backup Object Manager log. Backup Object Manager tries to restore the table space
to a location identical to the location in the original
system.
BKI8663W The Tablespace Definition Information
contains device containers of a type System action:
unsupported by BackOM redirected
User response: Make sure that the table space
restore.
mentioned can be restored to the original location. This
Explanation: A backup of a database using device requires that the user initiating the redirected restore
containers was requested. The backup was successful, it has the appropriate permissions for placing the table
can be used to restore the system, but it cannot be used space container in this location and that the table space
for restoring to a different location. Restoring to a can be restored without overwriting other data. In
different location is not supported with device order to avoid this situation in the future, the
containers. administrator of the source system may want to
recreate the table space according to the database
System action: characteristics Backup Object Manager expects.
User response: None.
BKI8668I Tablespace Definition Information
BKI8664E Connecting to 'alias' using CLI failed. created successfully.
The return code was return code. Explanation: The metadata concerning the phyiscal
Explanation: The system tried to connect to the database layout necessary for automatic redirected
database named via the CLI. The operation did not restores driven by BackOM were created successfully.
succeed and returned the error code indicated. System action:
System action: User response: None.
User response: Ensure that your database is enabled
to accept CLI connections. BKI8669I Free space of device with ID id
containing the container storage path
BKI8665I The backup timestamp is: timestamp 'storage_path' are free_space.

Explanation: The DB2 backup finished successfully Explanation: After assigning a container storage path
with the timestamp timestamp. to a dedicated device the remaining free space is
calculated and returned to the user.
System action:
System action:
User response: None.
User response: None.

BKI8666I Redirecting container of tablespace table

space with ID id. BKI8670I Remaining free space of device with ID
'id' after assigning container
Explanation: The named table space is restored to the 'container_name' of size size are free_space.
location requested.
Explanation: After assigning or creating a tablespace
System action: container on a dedicated device the remaining free
User response: None. space is calculated and returned to the user.
System action:
User response: None.

52 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8671I • BKI8705E

options to restrict the result set.

BKI8671I Using automatic storage path(s)
storage_path.
BKI8700E Internal parser error in Tablespace
Explanation: A dedicated automatic storage path will
Definition Information parser.
be used.
Explanation: An unexpected error occurred in the TDI
System action:
parser.
User response: None.
System action:
User response: Contact IBM Support.
BKI8672I Redefining container path(s) of
automatic storage tablespace tablespace
with ID id. BKI8701E This parser cannot process Tablespace
Definition Information version version.
Explanation: The path(s) an automatic storage
tablespace uses as a starting point for the container(s) Explanation: The current version of Backup Object
will be redefined. Manager is not compatible with the version the TDI
image was created with. As a consequence, the TDI
System action:
data cannot be processed.
User response: None.
System action:
User response: Check the release notes for the
BKI8690E Free space check for container 'path'
appropriate migration procedure.
failed. Only free bytes free space left on
device with ID 'id' but required bytes
required. BKI8702E Too many errors. Bailing out.
Explanation: The system requires a table space Explanation: The TDI parser encountered a number of
container of the size indicated at the path named, but errors. Restoring is stopped.
there is not sufficient free space available to create it.
System action:
System action:
User response: Check for and respond to preceding
User response: Try to make available the free space error messages in the Backup Object Manager log.
required, for example by 1. Removing some files on the
volume or file system the container is to reside on. 2.
Increasing the size of the file system the container is to BKI8703E Out of memory.
reside on. 3. Shrinking the size of the container Explanation: The TDI parser encountered a token that
requested so that it fits in the free space. Note: Backup cannot be read into the main memory. The TDI image
Object Manager assumes that a small part (0.05%) of cannot be processed, and restoring is stopped.
the free space will be required by the operating system
for administrative use. As a consequence, only 99.95% System action:
of the free space on the volume or file system is User response: Contact IBM Support.
actually available.

BKI8704E Error while reading input file.

BKI8692E The requested data could not be
retrieved. Explanation: The TDI parser tried to read more data
from disk or from TSM, but did not succeed.
Explanation: The TDI data of a backup image could
not be retrieved and displayed. System action:

System action: User response: Ensure that the TDI image to be

processed exists at the expected location and that the
User response: Look for and respond to preceding system has sufficient privileges to read it.
error messages.

BKI8705E Error in line line number.

BKI8693E More than one Tablespace Definition
Information file matches your query. Explanation: The TDI parser encountered a syntax
error in the line indicated. As a consequence, the TDI
Explanation: More than one TDI file matching the image cannot be analyzed.
search criteria was found on TSM.
System action:
System action:
User response: Respond to the error message and
User response: Specify additional BackOM command correct your TDI image.

Chapter 2. Tivoli Storage Manager for ERP messages 53

BKI8706E • BKI8730I

BKI8706E The container at 'path' is inappropriate BKI8711W Duplicate statement keyword ignored in
for tablespace tablespace. line line number.
Explanation: The container at the location indicated Explanation: At the line indicated, a duplicate
cannot be added to the table space named because of statement was encountered within a block. The system
incompatible properties. ignores the duplicate statement.
System action: System action:
User response: Check the properties of the container User response: Make sure to not specify duplicate
and the table space. Ensure that the IDs of the statements within a block.
containers are unique for the table space named.
BKI8715E Failed to create directory 'path'. Reason:
BKI8707E Missing statement keyword in block block reason
name near line line number.
Explanation: The path indicated could not be created.
Explanation: A keyword is missing in the named
System action: The operation stops. The operation
block ending at the line given.
cannot continue until the error is resolved.
System action:
User response: Check the properties of the path
User response: Insert the required statement in the indicated and make sure that its properties and the
block. properties of the parent directory are set accordingly.

BKI8708E The [TDI] header block must be the BKI8727E No instance found managing database
first block. 'database name'.
Explanation: The TDI image does not start with the Explanation: The DB2 instance, which manages the
required header ([TDI] block). Only comments or named database 'image_name' could not be detected.
whitespace are allowed before this block.
System action: Processing ends.
System action:
User response: Contact your IBM support personnel.
User response: Ensure that the [TDI] block is the first
block in the TDI image.
BKI8728E Could not attach to instance 'instance'.
Explanation: BackOM was not able to attach to the
BKI8709E The required block block name is
instance instance.
missing.
System action:
Explanation: The named block is missing in your TDI
image. User response: First, check the system environment
for possible instance candidates. Try the action again by
System action:
additionally specifying the BackOM command option
User response: Insert the missing block using valid '–i <instance name>'.
values.
BKI8729I Checking system resources ...
BKI8710W Duplicate block block name ignored at
Explanation: Prior to starting the redirected restore by
line line number.
BackOM the existing system resources, e.g. free space
Explanation: At the line indicated, a block begins of a file system will be checked.
whose name was encountered before. The system
System action:
ignores the duplicate block; it uses the data from the
first occurrence of duplicate blocks. User response: None.
System action:
BKI8730I Scaling tablespace containers to number
User response: Make sure that block names are
percent ...
unique within a TDI image.
Explanation: All table space containers will be
increased by the percentage indicated during the table
space container redefinition step.
System action:
User response: None.

54 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8731I • BKI8742E

containers of a combined size that is sufficient to hold

BKI8731I Normalizing tablespace containers ...
the used pages of the table space.
Explanation: All containers of a table space will be of
the same size after redefinition.
BKI8738E The container at path has a page size
System action: that is incompatible with its tablespace.
User response: None. Explanation: The container indicated does not have
the same page size as its table space according to the
definitions in the TDI image.
BKI8732E The Tablespace Definition Information
used with the redirected restore System action:
operation contains an invalid database
User response: Contact IBM Support.
alias.
Explanation: There is an invalid database alias
BKI8739E The type of the container at path is
specified in the alias statement of the TDI image.
incompatible with its tablespace.
System action:
Explanation: The container indicated cannot be used
User response: Provide a valid alias. with its associated table space according to the
definitions in the TDI image. SMS table spaces can only
have path containers, and DMS table spaces must have
BKI8733E The Tablespace Definition Information
file or device containers.
used with the redirected restore
operation contains an invalid instance System action:
name.
User response: Ensure that the appropriate types of
Explanation: There is an invalid database instance containers are used with each table space.
specified in the <instance> statement of the TDI image.
System action: BKI8740E The path path of a container must not be
relative.
User response: Provide a valid instance name.
Explanation: In the TDI image, the named path
defining a container does not seem to be a fully
BKI8734E The Tablespace Definition Information
qualified path.
used with the redirected restore
operation contains an invalid partition System action:
number.
User response: Ensure that all paths in your TDI are
Explanation: There is an invalid partition number fully qualified.
specified in the <Node> statement of the TDI image.
System action: BKI8741E The container at path would overwrite
existing files or directories.
User response: Provide a valid partition number.
Explanation: The TDI image contains the definition of
the container indicated whose location is already in
BKI8736E Tablespace tablespace must have at least
use. This is only allowed when restoring to the source
one container.
database. Restoring to a different location is stopped.
Explanation: The TDI image defines the table space
System action: Ensure that all path containers defined
named without containers.
in the TDI image point to non–existing paths and all
System action: file containers point to non–existing files.

User response: Ensure that there is at least one User response:

container associated with every table space.
BKI8742E The container at path is a device
BKI8737E Tablespace tablespace has containers with container which is not supported.
the combined storage too small.
Explanation: In the TDI image, a device container is
Explanation: The number of used pages of the table defined. However, device containers are not supported
space named exceeds the combined size of its table by Backup Object Manager.
space containers defined in the TDI image.
System action:
System action:
User response: Do not use device containers.
User response: Ensure that every table space has

Chapter 2. Tivoli Storage Manager for ERP messages 55

BKI8743I • BKI8752E

BKI8743I Local Tablespace Definition Information BKI8748E The Tablespace Definition Information
check returned return code. does not define enough storage to hold
all the data of the original database.
Explanation: The TDI with the target database table
space definition was checked. If the return code given Explanation: The target TDI has at least one table
does not equal 0 errors occurred. space whose containers are too small to hold the data
of the source database.
System action:
System action:
User response: In the case of a non–zero return code,
contact IBM Support. User response: Increase the container size or add
more containers to the table spaces.
BKI8744I Tablespace Definition Information
replacement check returned return code. BKI8749E The page size of a tablespace in the
Tablespace Definition Information does
Explanation: The system checked whether the table
not match the one of the original
space definitions of the target TDI can replace the
database.
definitions of the source TDI. If the return code given
does not equal 0 the table space definitions of the Explanation: The target TDI contains at least one table
target TDI are not valid. space with a matching ID in the source TDI, but their
page sizes do not match.
System action:
System action:
User response: In the case of a non–zero return code,
contact IBM Support. User response: Ensure that table spaces have the same
page sizes in both the source and the target TDI.
BKI8745E The Tablespace Definition Information
is invalid. BKI8750E The number of used pages of a
tablespace in the Tablespace Definition
Explanation: The TDI with the target table space
Information does not match the one of
definitions is not valid. Restoring to a different location
the original database.
is stopped.
Explanation: The target TDI contains at least one table
System action:
space with a matching ID in the source TDI, but the
User response: Check the Backup Object Manager log number of used pages of the target table space does not
for the return code of the validation. Check for and match the number of used pages in the original
respond to preceding error messages in the Backup database.
Object Manager log.
System action:
User response: Ensure that the number of used pages
BKI8746I The Tablespace Definition Information
of a table space is the same in both the source and the
is valid.
target TDI.
Explanation: The TDI with the target table space
definition is valid. Processing continues.
BKI8751E The tablespace type in the Tablespace
System action: Definition Information does not match
the one of the original database.
User response: None.
Explanation: The target TDI holds at least one table
space with a matching ID in the source TDI, but the
BKI8747E Not all tablespaces of the original table space types are different.
database are contained in the Tablespace
Definition Information. System action:
Explanation: At least one table space of the original User response: Ensure that the type of a table space is
database is missing in the TDI definitions of the target the same in both the source and the target TDI.
database. However, a new location must be given for
all table spaces of the original database. Therefore,
BKI8752E BackOM does not support redirected
restoring to a different location is stopped.
restore with device containers.
System action:
Explanation: The target TDI contains at least one
User response: Provide the information on the definition of a device container. However, device
missing table spaces and their containers. containers are not supported by Backup Object
Manager's redirected restore function.

56 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8753E • BKI8763E

System action:
BKI8759E Redirecting of at least one container
User response: Do not use the Backup Object failed.
Manager's redirected restore facility for device
Explanation: The system tried to create the containers
containers.
for a table space, but at least one of them could not be
redirected to a different location. Usually, the location
BKI8753E A container cannot be created at path. of one of the table space containers is not allowed. A
list of containers the system tries to create can be found
Explanation: Either the location where the table space in the Backup Object Manager log. One of them failed.
container is to be created does not exist, or the
permissions of the user are not sufficient. System action:

System action: User response: Check for and respond to further error
messages in the Backup Object Manager log.
User response: Check the location and the
permissions.
BKI8760E Directory 'directory' could not be created.

BKI8755I Getting reference Tablespace Definition Explanation: The system tried to create the directories
Information from TSM ... to place the containers in, but at least one failed.

Explanation: Retrieving the appropriate TDI to be System action:

used by internal checking routines from the TSM
User response: Ensure that the system has sufficient
server.
privileges to create the directories at the desired
System action: locations.
User response: None.
BKI8761E The container at path does not have the
minimum size of two extends.
BKI8756W Could not get reference Tablespace
Definition Information from TSM. No Explanation: A table space container to be created
input validation is done. must have at least the size of two extends.
Explanation: The system could not find a TDI image System action:
matching the database backup to be restored on TSM.
User response: Correct the size of the container to be
The restore action will be continued, but the input data
created.
cannot be validated before the restore starts.
System action:
BKI8762I Set tablespace container with ID id and
User response: None. name 'tablespace_container'.
Explanation: Backup Object Manager redirects a table
BKI8757I Performing redirected restore from space container to the ID and name indicated.
'source alias' to 'target alias' ...
System action:
Explanation: Redirected restore of source alias to target
User response: None.
alias is starting.
System action:
BKI8763E The extent size of a tablespace in the
User response: None. Tablespace Definition Information does
not match the one of the original
database.
BKI8758E The Tablespace Definition Information
does not contain data for tablespace Explanation: The extend sizes of corresponding table
'tablespace'. spaces defined in the source and target TDIs must be
equal. However, for at least one table space different
Explanation: A definition of the table space named is extend sizes are defined in the source and target
expected to be provided in the TDI, but could not be databases.
found.
System action:
System action:
User response: Define matching extend sizes for
User response: Ensure that all table spaces of the corresponding table spaces.
source database are also defined in the target TDI.

Chapter 2. Tivoli Storage Manager for ERP messages 57

BKI8765I • BKI8776E

automatic redirected restore driven by BackOM.

BKI8765I Checking redirected restore from 'source
alias' to 'target alias' ... System action:
Explanation: The system is testing whether the User response: Contact your IBM support personnel.
original database can be restored to the target location.
It checks whether v the file system where the table
space containers are to be created has sufficient free BKI8770I Getting Tablespace Definition
space. (If specified, normalizing and scaling are also Information used with the redirected
considered.) v there are existing files and directories restore operation from TSM...
identical to the containers defined for the target Explanation: The system is retrieving the TDI image
database. This would indicate that a database of same from the TSM server.
name and of same structure already exists, and data
could be overridden. v the structures of the source and System action:
target databases (table space types, page sizes, extend User response: None.
sizes) allow for a redirected restore.
System action: BKI8771E The Tablespace Definition Information
User response: None. used with the redirected restore
operation could not be retrieved.

BKI8766I Check successful. Redirected restore Explanation: The TDI image specified could not be
possible with these settings. found.

Explanation: The redirected restore test finished System action:

successfully. Thus, the redirected restore operation can User response: Provide the correct location of the TDI
be started with the options specified for the test run. image.
System action:
User response: None. BKI8772E The selected database has a structure
that prevents automatic cloning.

BKI8767W Warnings occurred. Explanation: You tried to clone an SAP database using
redirected restore, but the database does not have the
Explanation: The redirected restore test detected one default directory structure of an SAP database. The
or more minor conflicts. These conflicts may or may cloning facility of Backup Object Manager redirected
not prevent a successful redirected restore operation. restore cannot be used for this system.
Nevertheless, it is recommended to resolve them.
System action:
System action:
User response: You may use either the interactive or
User response: Check for and respond to preceding the batch mode of Backup Object Manager redirected
warning messages in the Backup Object Manager log. restore.

BKI8768E Check failed. Redirected restore not BKI8773E The interactive modification of the
possible with these settings. containers failed.
Explanation: The redirected restore test detected one Explanation: You tried to interactively change the
or more major errors which will prevent a successful location of containers, but this operation failed.
redirected restore with these settings.
System action: Processing ends.
System action:
User response: Contact IBM Support.
User response: Check for and respond to preceding
error messages in the Backup Object Manager log.
BKI8776E You are not allowed to delete this
container.
BKI8769E Found multiple Tablespace Definition
Information matching the given Explanation: You tried to delete the last container of a
timestamp. Additional search conditions table space. However, at least one container must be
needed. available to every table space.

Explanation: More than one TDI file for a database System action:
backup image was found on the TSM server. In such a User response: Make sure that there is at least one
scenario, the integrity of the metadata assigned to a container defined for every table space.
database backup images is violated and prevents an

58 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8798E • BKI8810I

BKI8798E Due to errors, you cannot continue the BKI8804W The recovery log could not be written.
operation.
Explanation: After every backup or restore, Data
Explanation: You tried to start a restore operation Protection for SAP writes a record into the recovery log
after redefining the containers interactively, but errors file tdprlf.<SID>.node_name.log. It is located in the path
were detected in the input data. The operation cannot pointed to by environment variable TDP_DIR.
continue.
System action:
System action:
User response: Check, if the permissions are set
User response: Check all table spaces with '!!' error correctly and if there is sufficient free space in your file
marks in the list and correct the definitions of their system.
containers. Then continue.
BKI8805I The restore was cancelled by the user.
BKI8799E A container must have a size of at least Existing data not overwritten.
twice the extent size (minimum size for
Explanation: The existing database is still operational.
this tablespace).
System action:
Explanation: The container size specified is too small.
The minimum size of a container is twice the extent User response: None.
size.
System action: BKI8806I product version.release.modification.level
(build_numberbeta) build_date
User response: Correct the container size.
Explanation: Writes version information into the
product log file.
BKI8800I The command is: command
System action:
Explanation: Displays the command that was issued.
The following commands are possible: Backup, Restore, User response: None.
Archive/Retrieve.
System action: BKI8807I Archive log file 'log number' of chain 'log
chain number'.
User response: None.
Explanation: Writes information about the log file to
be archived into the product log file.
BKI8801I Time: time ––– PID: PID_Number
System action:
Explanation: Displays the process id of the DB2
process which called the shared library. User response: None.
System action:
BKI8808I Retrieve log file 'log number' of chain 'log
User response: None.
chain number'. Seeking for TSM image
'image'.
BKI8802I Found number type image(s) on TSM
Explanation: Writes information about the log file to
server.
be retrieved into the product log file.
Explanation: For restore and delete operations Data
System action:
Protection for SAP queries TSM for backup images by
means of a timestamp and shows the number of found User response: None.
images.
System action: BKI8810I Cleaning up resources of process
PID_number'.
User response: None.
Explanation: All resources used by the product will be
released.
BKI8803I The DB2 image size for this session is
about 'size'. System action:
Explanation: The estimated size of the data to be User response: None.
backed up is displayed.
System action:
User response: None.

Chapter 2. Tivoli Storage Manager for ERP messages 59

BKI8812I • BKI8822I

BKI8812I Committed TSM sessions of this backup BKI8818W Invalid value specified for
run will be deleted. BACKOM_LOCATION.
Explanation: During a backup with multiple sessions, Explanation: The BackOM executable was not started
an error occurred. The backup operation is stopped. for collecting database metadata due to an invalid
TSM sessions already committed during this operation specification.
are being deleted from the TSM server in order to
System action:
prevent them from being considered restorable.
User response: Check the value of the TSM for ERP
System action:
configuration parameter BACKOM_LOCATION. The
User response: None. parameter can be found in the vendor environment file
and must contain the fully qualified name of the
BackOM executable.
BKI8813E Error deleting committed TSM sessions.
Explanation: One or more committed TSM sessions
BKI8819I The TSM objects matching with mask
could not be deleted during the postprocessing of the
'search mask' will be deleted.
failed backup run.
Explanation: The cleanup of a failed TSM for ERP
System action:
database backup will delete any partial TSM backup
User response: Use the Backup Object Manager to image of that run already stored on the TSM server and
delete the file(s) manually. matching search mask .
System action:
BKI8814I Inquired TSM with mask 'search mask'.
User response: None.
Explanation: The string denoted is used to inquire
TSM for backup images.
BKI8820E No valid TSM session found.
System action:
Explanation: A running TSM for ERP workflow could
User response: None. not continue due to a missing TSM session.
System action:
BKI8815I Information for Log Manager:
User response: Contact your IBM support personnel.
DB2_instance DB2_database_name
DB2_database_alias
log_and_log_chain_number partition BKI8821I Using option(s) 'options'.
Explanation: The information listed is provided to the Explanation: The options string specifies vendor
DB2 Log Manager. options that DB2 provides to the TSM for ERP library
as part of the calling function. These could be options
System action:
directly provided as part of the database backup or
User response: None. restore command or options made persistent in the
database configuration, here the parameters
VENDOROPT, LOGARCHOPT1 or LOGARCHOPT2.
BKI8816I DB2 version 'version' detected.
System action:
Explanation: TSM for ERP is running on a system
where DB2 version version is set up. User response: None.

System action:
BKI8822I Configuration parameter(s):parameters
User response: None.
Explanation: The list specifies a set of runtime
parameters that the TSM for ERP library is using for
BKI8817I No corresponding committed TSM the calling workflow.
session(s) found. Nothing will be
deleted. System action:
Explanation: The cleanup of a failed TSM for ERP User response: None.
database backup could not find any partial TSM
backup image of that run already stored on the TSM
server for deletion.
System action:
User response: None.

60 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI8823W • BKI9009W

XINT_NLS_CATALOG_PATH is mandatory.
BKI8823W Configuration parameter
SRC_DB_ALIAS requires parameter System action: Processing stops.
SRC_DB_INSTANCE and vice versa.
User response: The environment variable
Explanation: To be able to recover a database after a XINT_NLS_CATALOG_PATH may be required..
redirected restore using the built–in DB2 rollforward
command, TSM for ERP needs both SRC_DB_ALIAS
and SRC_DB_INSTANCE. BKI9005E A not supported by B

System action: Explanation: The installed version of product B does

not support product A. Most likely you need to
User response: Include both parameters upgrade product B.
SRC_DB_ALIAS and SRC_DB_INSTANCE in the TSM
for ERP vendor environment file and retry the database System action:
recovery. User response: Contact the IBM Support.

BKI8899E Interface problem in function function: BKI9006E Internal error while reading
Value 'value' of parameter 'parameter' is environment variable: variable
not supported with DB2 version 'version'.
Explanation: This is an internal error.
Explanation: An unknown action code during the
program execution was encountered. System action:

System action: User response: Contact IBM Support.

User response: Contact your IBM support personnel.

BKI9007W An error occurred while terminating the
application:the error
BKI9001E Internal error: error
Explanation: While terminating the application, an
Explanation: The following internal error: error has error occurred. This has no impact on the success of the
been encountered. operation.
System action: System action:
User response: Contact IBM Support. User response: None.

BKI9002E Parameter 'all' is not supported. BKI9008E This product requires at least version
Explanation: The provided parameter is not number of product name to be installed.
supported. This error can be caused by nodes that are Explanation: The version of the application product
specified without being separated by commas. name is not supported by this application. Most likely
System action: Processing ends. application product name needs to be upgraded.

User response: Make sure the specified nodes are System action:
separated by commas, then try the command again. User response: Contact IBM Support.

BKI9003E Incompatible components installed: BKI9009W The following products are not
component name one, component name two compatible: product name first (product
Explanation: The components mentioned in the version first) and product name second
message text can not be used together. This may be the (product version second).
result of an incomplete upgrade. Explanation: This message is similar to BKI9008E. But
System action: in this case it's not obvious which one of the products
needs to be upgraded.
User response: Contact IBM Support.
System action:

BKI9004E Location of the message catalog could User response: Contact IBM Support.
not be figured out.
Explanation: Data Protection for SAP locates the
message catalog over the install directory. When Data
Protection for SAP is exploited through a library like
DB2 or Oracle/RMAN, then the environment variable

Chapter 2. Tivoli Storage Manager for ERP messages 61

BKI9010E • BKI9200E

BKI9010E Could not determine installation BKI9015E Failed to locate functions in library:
directory for program. Please restart the library reason: reason
process using a fully qualified name.
Explanation: One or more functions could not be
Explanation: The name of the path where a given found in the ACS library.
program is located could not be determined.
System action:
System action:
User response: Contact your IBM support personnel.
User response: Contact your IBM support personnel.
BKI9198E While processing path path_name, an
BKI9011E There was no response received within error occurred. The following error
number seconds; timeout is expired. You information was received:
can increase the timeout by specifying detailed_error_information
the profile parameter timeoutphase for the
Explanation: This message indicates that a problem
current phase of the backup or restore
occurred while processing the following path:
operation.
path_name. If you are protecting data for DB2
Explanation: The communication between two applications, this path contains one or more of the
program components was suspended or stopped, database files to be included in the operation. If you
which can lead to a timeout. are protecting data for Oracle databases or the Custom
Application Agent, this path was provided in the in-file
System action:
specified with the flag "-I <infile_name>" in the
User response: Increase the timeout by specifying the command.
profile parameter TIMEOUT_<PHASE> for the current
System action: The operation stops. The operation
phase of the backup or restore operation. If this does
cannot continue until the error is resolved.
not solve the probblem please contact your IBM
support personnel. User response: To help resolve the problem the
detailed_error_information is available. After you resolve
the issue, enter the command again.
BKI9012E One of the requested data containers is
already the subject of a restore.
BKI9199E The following command returned with
Explanation: A restore of the same data has already
an error: command The return code from
been requested.
this command is return_code The
System action: Processing stops. following command output was
received: command_output Additional
User response: Multiple restore operations are usually support information: An exception was
prevented by the database system. If there are no thrown at position: position(line).
multiple restore operations performed concurrently,
then contact IBM support for this problem. Explanation: This message indicates that the command
returned with the error indicated by return_code. Any
additional command_output is provided.
BKI9013E Concurrent restore of objects being
backed up with multiple device agents System action: The operation stops. The operation
is not supported. cannot continue until the error is resolved.

Explanation: This special restore scenario is User response: To help resolve the problem the
unsupported. command_output is available. After you resolve the
issue, enter the command again.
System action:
User response: Contact your IBM support personnel. BKI9200E Additional support information: An
exception was thrown at position:
BKI9014E Failed to load library: library reason: position(line).
reason Explanation: This error message typically follows a
Explanation: The ACS library could not be loaded. previous error. If so this error message can be ignored.
Otherwise contact IBM Support.
System action:
System action:
User response: Contact your IBM support personnel.
User response: Contact IBM Support.

62 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI9201E • BKI9211E

Otherwise contact IBM Support.

BKI9201E Additional support information: An
exception was thrown at position: System action:
position(line).
User response: Contact IBM Support.
Explanation: This error message typically follows a
previous error. If so this error message can be ignored.
Otherwise contact IBM Support. BKI9207E Additional support information: An
exception was thrown at position:
System action: file(line).
User response: Contact IBM Support. Explanation: This error message typically follows a
previous error. If so this error message can be ignored.
Otherwise contact IBM Support.
BKI9202E Additional support information: An
exception was thrown at position: System action:
position(line).
User response: Contact IBM Support.
Explanation: This error message typically follows a
previous error. If so this error message can be ignored.
Otherwise contact IBM Support. BKI9208E System error errno: errno text at position:
file(line).
System action:
Explanation: A system call failed with errno.
User response: Contact IBM Support.
System action:

BKI9203E Additional support information: An User response: Check errno and errno text with you
exception was thrown at position: system administrator. If you cannot resolve the
position(line). problem, contact IBM Support.

Explanation: This error message typically follows a

previous error. If so this error message can be ignored. BKI9209E Additional support information: No
Otherwise contact IBM Support. handler registered for message type
message. Thrown at position: file(line).
System action:
Explanation: This error message typically follows a
User response: Contact IBM Support. previous error. If so this error message can be ignored.
Otherwise contact IBM Support.
BKI9204E Additional support information: An System action:
exception was thrown at position:
file(line) (text_description). User response: Contact IBM Support.

Explanation: This error message typically follows a

previous error. If so this error message can be ignored. BKI9210E ESD_AbortDispatchingException thrown
Otherwise contact IBM Support. at position: file(line).

System action: Explanation: An internal error occurred.

User response: Contact IBM Support. System action:

User response: Contact IBM Support.
BKI9205E Additional support information: Unable
to instantiate name at file(line). BKI9211E Additional support information: An
Explanation: This error message typically follows a exception was thrown at position:
previous error. If so this error message can be ignored. file(line). (State state)
Otherwise contact IBM Support. Explanation: This error message typically follows a
System action: previous error. If so this error message can be ignored.
Otherwise contact IBM Support.
User response: Contact IBM Support.
System action:

BKI9206E Additional support information: Unable User response: Contact IBM Support.
to use actual when expecting expected at
file(line).
Explanation: This error message typically follows a
previous error. If so this error message can be ignored.

Chapter 2. Tivoli Storage Manager for ERP messages 63

BKI9212E • BKI9222E

BKI9212E Additional support information: No BKI9217E Additional support information: An

handler registered for message type exception was thrown at position:
(message_type, classname). Thrown at file(line).
position: file(line).
Explanation: This error message typically follows a
Explanation: This error message typically follows a previous error. If so this error message can be ignored.
previous error. If so this error message can be ignored. Otherwise contact IBM Support.
Otherwise contact IBM Support.
System action:
System action:
User response: Contact IBM Support.
User response: Contact IBM Support.
BKI9218E Additional support information: An
BKI9213E A memory allocation request failed at exception was thrown at position:
position: file(line). file(line).
Explanation: This error message indicates an Explanation: This error message typically follows a
out–of–storage condition. It may occur due to a previous error. If so this error message can be ignored.
previous error, or it may be owed to a large size of the Otherwise contact IBM Support.
internal buffers.
System action:
System action:
User response: Contact IBM Support.
User response: Check for and respond to preceding
error messages. You may also want to reduce the size
BKI9219E Additional support information: Invalid
of the internal buffers (keyword BUFFSIZE in the Data
error type type encountered.
Protection for SAP profile).
Explanation: This error message typically follows a
previous error. If so this error message can be ignored.
BKI9214E Additional support information: An
Otherwise contact IBM Support.
exception was thrown from a destructor.
System action:
Explanation: This error message typically follows a
previous error. If so this error message can be ignored. User response: Contact IBM Support.
Otherwise contact IBM Support.
System action: BKI9220E Additional support information: Second
call of call.
User response: Contact IBM Support.
Explanation: This error message typically follows a
previous error. If so this error message can be ignored.
BKI9215E The maximum string length supported
Otherwise contact your IBM Support.
for name is length.
System action:
Explanation: The supported string length of a system
component, e.g. file name or hostname has been User response: Contact your IBM Support.
violated.
System action: BKI9221E The operation ended prematurely with
return code rc. An exception was thrown
User response: Check the components involved in the
at position: file(line).
operation. If the problem cannot be resolved contact
your IBM support personnel. Explanation: An operation could not be finished
successfully due to an unexpected termination.
BKI9216E Additional support information: An System action:
exception was thrown at position:
file(line). User response: Check the logs for further information.
If the problem cannot be resolved contact your IBM
Explanation: This error message typically follows a support personnel.
previous error. If so this error message can be ignored.
Otherwise contact IBM Support.
BKI9222E A snapshot–type operation was
System action: interrupted, Additional support
information: An exception was thrown
User response: Contact IBM Support.
at position: file(line).
Explanation: A snapshot operation could not be

64 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI9223E • BKI9231E

finished successfully due to an unexpected interruption.

BKI9227E The ASM diskgroup 'diskgroup' has not
System action: been found. Ensure that it is available.

User response: Check the logs for further information. Explanation: The specified diskgroup is needed for
If the problem cannot be resolved contact your IBM the backup but it has not been found in the ASM
support personnel. instance.
System action: Processing ends.
BKI9223E The operation will be aborted.
User response: Please ensure that the diskgroup is
Explanation: An internal error during an operation available in your ASM instance and that it is mounted.
leads to an abort of that operation.
System action: BKI9228E Excpected ASM file but found file: 'file'

User response: Check the logs for further information. Explanation: ASM files were expected, but a non-ASM
If the problem cannot be resolved contact your IBM file has been found. This might occur if your database
support personnel. resides on ASM and non-ASM files.
System action: Processing ends.
BKI9224E The operation will be aborted. Check
User response: Please ensure that you do not have a
for other error messages in the log files.
mixed environment with ASM and non-ASM files.
Explanation: An internal error during an operation
leads to an abort of that operation.
BKI9229E Excpected file but found ASM file: 'file'
System action:
Explanation: Non-ASM files were expected, but an
User response: Check the logs for further information. ASM file has been found. This might occur if your
If the problem cannot be resolved contact your IBM database resides on ASM and non-ASM files.
support personnel.
System action: Processing ends.
User response: Please ensure that you do not have a
BKI9225E The keyword 'keyword' has not been
mixed environment with ASM and non-ASM files.
found in the line 'line' of the file
'file_name'. Please change it back to the
original value if you modified it. BKI9230E The SSL/TLS certificate provided by the
server is missing a valid subject DN or
Explanation: Occurs for example if the entries in the
issuer DN field.
file /etc/inittab have been modified before a second
installation. Explanation: The subject DN or issuer DN field of the
certificate provided by the server is missing. Both fields
System action:
are mandatory fields to allow a validation of the
User response: Change the modified line in the certificate.
file_name back to the original value, keyword gives a hint
System action: The task stopped before successfully
to what is expected.
completing.
User response: Import a valid server certificate to the
BKI9226E The ASM instance with SID='instance id'
key ring database 'fcmcert.kdb'.
is not available. Please check if the
ASM_INSTANCE_ID is set to the right
ASM instance, if yes start it and check BKI9231E The SSL/TLS certificate provided by the
the availability. server is not proving its supposed
identity.
Explanation: The ASM instance with the specified SID
could not be accessed. Explanation: The SSL/TLS certificate provided by the
server is not issued for the server that was supposed to
System action: Processing ends.
connect. The alternative name or subject CN field of the
User response: Check if the ASM instance with the certificate does not match the hostname or IP address
specified SID is available and started. of the server that was actually connected.
System action: The task stopped before successfully
completing.
User response: Revalidate the correctness of the
certificate that has been imported to the key ring
database 'fcmcert.kdb'. Its alternative name or subject

Chapter 2. Tivoli Storage Manager for ERP messages 65

BKI9300E • BKI9312E

CN field needs to match the hostname or IP address as

BKI9308E A socket request timed out after
stated in the IBM Tivoli Storage FlashCopy Manager
processing number of bytes bytes. file(line).
profile (GLOBAL section, parameter ACSD).
Explanation: A socket request was issued with a
timeout and the requested action could not be
BKI9300E Additional support information:
completed within the time specified. It was cancelled
Aborting 'send' operation. See previous
after processing number of bytes bytes.
error.
System action:
Explanation: This error may have been caused by
previous errors. User response: If you need to call IBM Support,
provide the information given in this message together
System action:
with the error information.
User response: Check for previous errors and correct
them.
BKI9309E Operation terminated due to an explicit
abort request.
BKI9301E Additional support information: State
Explanation: An operation was terminated due to
state does not match state pattern pattern.
customer intervention.
Explanation: This error message typically follows a
System action:
previous error. If so this error message can be ignored.
Otherwise contact IBM Support. User response: None.
System action:
BKI9310E Could not add backup_id to the
User response: Contact your IBM Support.
repository at path.
Explanation: The system was not able to add
BKI9302E Additional support information: A
information on the named backup to the repository
process ended unexpectedly. Check
located in the path indicated.
previous error messages.
System action:
Explanation: This error message typically follows a
previous error. If so this error message can be ignored. User response: Make sure the repository path is set
Otherwise contact your IBM Support. correctly. If you need to correct the repository location,
restart the server executable afterwards. If the problem
System action: Processing ends
persists contact your IBM support personnel.
User response: Contact your IBM Support.
BKI9311E Could not find backup_id in the
BKI9306I Dumping callstack. repository at path.

Explanation: This message is always preceded by an Explanation: Information on the backup denoted by
error message indicating the problem. It provides the backup ID could not be found in the repository
additional information that might help IBM Support to located in the path indicated.
analyze the cause of the problem.
System action:
System action:
User response: Make sure the repository path is set
User response: If you need to call IBM Support, correctly. If you need to correct the repository location,
provide the information given in this message together restart the server executable afterwards. If the problem
with the error information. persists contact your IBM support personnel.

BKI9307E Did not find a winsock dll compatible BKI9312E backup_id is currently locked in the
with version major_winsock repository at repository.
version.minor_winsock_version. Version
Explanation: The information on the backup denoted
found is low_byte_available
by the backup ID is currently locked by a different
version.high_byte_available_version.
process. Make sure to run only a single operation using
Explanation: The product failed to load the a specific backup at a time.
appropriate winsock dll.
System action:
System action:
User response: Wait for the other operation to finish
User response: Contact your system administrator. or abort this operation. Then start again. If the problem
persists contact your IBM support personnel.

66 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 BKI9313E • BKI9329E

Explanation: The length of the specified backup id is

BKI9313E Failed to update backup_id in the
incorrect.
repository at path.
System action:
Explanation: The information on the named backup
could not be updated in the repository located at the User response: Correct the length of the backup id to
path named. match the specified length.
System action:
BKI9318E The file 'filename' has not been found. It
User response: Check the logs for other messages
is required for the device agent to
pointing to the cause of this problem. Resolve any
function. Check your installation.
problems indicated. If the problem persists contact your
IBM support personnel. Explanation: The specified file has not been found
even though it was included in the installation.
BKI9314E Could not remove backup_id from the System action:
repository at path.
User response: Check that the specified file is
Explanation: An attempt to remove the information available in the specified location. Consider installing
on the backup named from the repository located at the the product again in order to make the file available.
path indicated failed.
System action: BKI9328E An error occurred in the secure
communication layer when running the
User response: Check the logs for other messages
following function: function. GSKit
pointing to the cause of this problem. Resolve any
return code: numeric return code. GSKit
problems indicated. If the problem persists contact your
error: return value.
IBM support personnel.
Explanation: Information about the error is provided
in the return value.
BKI9315E Could not access the repository at 'path'
because it is currently locked by another System action: The task stopped before successfully
process. completing.
Explanation: When starting up, the server tried to User response: Resolve the problem identified in the
load the repository located at the path named. return value. Try the operation again.
However, the repository was locked by a different
process. This can happen if two server processes try to
use the same repository. This is not supported. BKI9329E An error occurred when the software
tried to link the SSL Implementation to
System action: GSKit. GSKitWrapper error: 'linker error'
User response: Make sure each instance of the server Explanation: Information about the error is provided
uses its own repository. in linker error.
System action: The task stopped before successfully
BKI9316E The name 'name' refers to an existing file completing.
or directory, but it does not appear to be
a valid repository. In order to continue User response: Resolve the problem identified in the
you need to specify either a non existing linker error. Try the operation again.
directory or the path of an existing valid
repository.
Explanation: The server could not locate its repository
when it started.
System action:
User response: Correct the profile or the call as
appropriate.

BKI9317E The specified backup id 'backup_id' must

have char_count characters. If the
specified amount of characters exists,
make sure there are no special
characters.

Chapter 2. Tivoli Storage Manager for ERP messages 67

68 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages
Appendix A. Tivoli support information
You can find support information for Tivoli and other IBM products from various
sources.

From the IBM Support Portal at http://www.ibm.com/support/entry/portal/, you

can select the products that you are interested in and search for a wide variety of
relevant information.

Communities and other learning resources

In addition to product documentation, many forms of assistance are available to
help you get started as you deploy and use the Tivoli Storage Manager family of
products. These resources can also help you to solve problems that you might
have.

You can use forums, wikis, and other social media tools to ask questions, talk to
experts, and learn from others.

User groups
Tivoli Global Storage Virtual User Group
Access this user group at http://www.tivoli-ug.org/storage.
This group makes it possible for individuals from many different industries
and types of organizations to share information and work directly with the
IBM product experts. Local chapters also exist where members meet in
person to share experiences and hear from guest speakers.
ADSM.ORG
Access this mailing list at http://adsm.org.
This independently managed Storage Management discussion forum
started when Tivoli Storage Manager was known as ADSTAR Distributed
Storage Manager (ADSM). The members of this forum have many years of
experience with Tivoli Storage Manager in almost every type of IT
environment.
To subscribe to the forum, send an email to [email protected]. The
body of the message must contain the following text: SUBSCRIBE ADSM-L
your_first_name your_family_name.

Tivoli Storage Manager community on Service Management

Connect

Access Service Management Connect at http://www.ibm.com/developerworks/

servicemanagement. In the Storage Management community of Service
Management Connect, you can connect with IBM in the following ways:
v Become involved with transparent development, an ongoing, open engagement
between users and IBM developers of Tivoli products. You can access early
designs, sprint demonstrations, product roadmaps, and prerelease code.
v Connect one-on-one with the experts to collaborate and network about Tivoli
and the Tivoli Storage Manager community.
v Read blogs to benefit from the expertise and experience of others.

© Copyright IBM Corp. 1993, 2014 69

 v Use wikis and forums to collaborate with the broader user community.

Tivoli Storage Manager wiki on developerWorks®

Access this wiki at https://www.ibm.com/developerworks/servicemanagement/

sm/index.html.

Find the latest best practices, white papers, and links to videos and other
resources. When you log on, you can comment on content, or contribute your own
content.

Tivoli Support Technical Exchange

Find information about upcoming Tivoli Support Technical Exchange webcasts at

http://www.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html.
Replays of previous webcasts are also available.

Learn from technical experts who share their knowledge and then answer your
questions. The sessions are designed to address specific technical issues and
provide in-depth but narrowly focused training.

Other social media sites

LinkedIn
You can join groups on LinkedIn, a social media site for professionals. For
example:
v Tivoli Storage Manager Professionals: http://www.linkedin.com/
groups/Tivoli-Storage-Manager-Professionals-54572
v TSM: http://www.linkedin.com/groups?gid=64540
Twitter
Follow @IBMStorage on Twitter to see the latest news about storage and
storage software from IBM.

Tivoli education resources

Use these education resources to help you increase your Tivoli Storage Manager
skills:
Tivoli Education and Certification website
View available education at http://www.ibm.com/software/tivoli/
education.
Use the Search for Training link to find local and online offerings of
instructor-led courses for Tivoli Storage Manager.
Education Assistant
Access resources at http://publib.boulder.ibm.com/infocenter/ieduasst/
tivv1r0/index.jsp.
Scroll to view the list of available training videos. Recorded product
demonstrations are also available on a YouTube channel.

70 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

Searching knowledge bases
If a problem occurs while you are using one of the Tivoli Storage Manager family
of products, you can search several knowledge bases.

Begin by searching the IBM product documentation at http://www.ibm.com/

support/knowledgecenter/. You can enter words, phrases, or message numbers in
the Search field to find relevant topics.

Searching the Internet

If you cannot find an answer to your question in the IBM Knowledge Center,
search the Internet for the information that might help you resolve the problem.

To search multiple Internet resources, go to the IBM support website at

http://www.ibm.com/support/entry/portal/. You can search for information
without signing in.

Sign in using your IBM ID and password if you want to customize the site based
on your product usage and information needs. If you do not already have an IBM
ID and password, click Sign in at the top of the page and follow the instructions
to register.

From the support website, you can search various resources:

v IBM technotes.
v IBM downloads.
v IBM Redbooks® publications.
v IBM Authorized Program Analysis Reports (APARs). Select the product and click
Downloads to search the APAR list.

Using IBM Support Assistant

IBM Support Assistant is a complimentary software product that can help you with
problem determination. It is available for some Tivoli Storage Manager and Tivoli
Storage FlashCopy Manager products.

IBM Support Assistant helps you gather support information when you must open
a problem management record (PMR), which you can then use to track the
problem. The product-specific plug-in modules provide you with the following
resources:
v Support links
v Education links
v Ability to submit problem management reports

You can find more information and download the IBM Support Assistant web page
at http://www.ibm.com/software/support/isa.

You can also install the stand-alone IBM Support Assistant application on any
workstation. You can then enhance the application by installing product-specific
plug-in modules for the IBM products that you use. Find add-ons for specific
products at http://www.ibm.com/support/docview.wss?uid=swg27012689.

Appendix A. Tivoli support information 71

 Finding product fixes
A product fix to resolve a software problem might be available from the IBM
software support website.

Procedure

Determine what fixes are available by checking the IBM software support website
at http://www.ibm.com/support/entry/portal/.
If you previously customized the site based on your product usage:
1. Click the link for the product, or a component for which you want to
find a fix.
2. Click Downloads, and then click Search for recommended fixes.
If you have not previously customized the site:
Click Downloads and search for the product.

Receiving notification of product fixes

You can receive notifications about fixes, flashes, upgrades, and other news about
IBM products.

Procedure
1. From the support page at http://www.ibm.com/support/entry/portal/, click
Sign in and sign in using your IBM ID and password. If you do not have an
ID and password, click register now and complete the registration process.
2. Click Manage all my subscriptions in the Notifications pane.
3. Click the Subscribe tab, and then click Tivoli.
4. Select the products for which you want to receive notifications and click
Continue.
5. Specify your notification preferences and click Submit.

Contacting IBM Software Support

You can contact IBM Software Support if you have an active IBM subscription and
support contract, and if you are authorized to submit problems to IBM.

Procedure
1. Ensure that you have completed the following prerequisites:
a. Set up a subscription and support contract.
b. Determine the business impact of the problem.
c. Describe the problem and gather background information.
2. Follow the instructions in “Submitting the problem to IBM Software Support”
on page 74.

72 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

Setting up and managing support contracts
You can set up and manage your Tivoli support contracts by enrolling in IBM
Passport Advantage®. The type of support contract that you need depends on the
type of product you have.

Procedure

Enroll in IBM Passport Advantage in one of the following ways:

v Online: Go to the Passport Advantage website at http://www.ibm.com/
software/lotus/passportadvantage/, click How to enroll, and follow the
instructions.
v By telephone: For critical, system-down, or high-severity issues, you can call
1-800-IBMSERV (1-800-426-7378) in the United States. For the telephone number
to call in your country, go to the IBM Software Support Handbook web page at
http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html
and click Contacts.

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you must understand and assess the business impact of the problem
you are reporting.

Severity level Description

Severity 1 Critical business impact: You are unable to use the program,
resulting in a critical impact on operations. This condition
requires an immediate solution.
Severity 2 Significant business impact: The program is usable but is
severely limited.
Severity 3 Some business impact: The program is usable with less
significant features (not critical to operations) unavailable.
Severity 4 Minimal business impact: The problem causes little impact on
operations, or a reasonable circumvention to the problem has
been implemented.

Describing the problem and gathering background information

When explaining a problem to IBM, it is helpful to be as specific as possible.
Include all relevant background information so that IBM Software Support
specialists can help you solve the problem efficiently.

To save time, know the answers to these questions:

v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can the problem be re-created? If so, what steps led to the failure?
v Have any changes been made to the system? For example, hardware, operating
system, networking software, and so on.
v Are you using a workaround for this problem? If so, be prepared to explain it
when you report the problem.

Appendix A. Tivoli support information 73

 Submitting the problem to IBM Software Support
You can submit the problem to IBM Software Support online or by telephone.
Online
Go to the IBM Software Support website at http://www.ibm.com/
support/entry/portal/Open_service_request/Software/
Software_support_(general). Sign in to access IBM Service Requests and
enter your information into the problem submission tool.
By telephone
For critical, system-down, or severity 1 issues, you can call 1-800-IBMSERV
(1-800-426-7378) in the United States. For the telephone number to call in
your country, go to the IBM Software Support Handbook web page at
http://www14.software.ibm.com/webapp/set2/sas/f/handbook/
home.html and click Contacts.

74 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

Appendix B. Accessibility features for the Tivoli Storage
Manager product family
Accessibility features help users who have a disability, such as restricted mobility
or limited vision to use information technology products successfully.

Accessibility features

The IBM Tivoli Storage Manager family of products includes the following
accessibility features:
v Keyboard-only operation using standard operating-system conventions
v Interfaces that support assistive technology such as screen readers

The command-line interfaces of all products in the product family are accessible.

Tivoli Storage Manager Operations Center provides the following additional

accessibility features when you use it with a Mozilla Firefox browser on a
Microsoft Windows system:
v Screen magnifiers and content zooming
v High contrast mode

The Operations Center and the Tivoli Storage Manager Server can be installed in
console mode, which is accessible.

The IBM Knowledge Center is enabled for accessibility. Read about the accessibility
features online at http://www.ibm.com/support/knowledgecenter/doc/
kc_help.html#accessibility.

Vendor software

The Tivoli Storage Manager product family includes certain vendor software that is
not covered under the IBM license agreement. IBM makes no representation about
the accessibility features of these products. Contact the vendor for the accessibility
information about its products.

IBM and accessibility

See the IBM Human Ability and Accessibility Center (http://www.ibm.com/able)

for information about the commitment that IBM has to accessibility.

© Copyright IBM Corp. 1993, 2014 75

76 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages
Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,

contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM websites are provided for

convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for this IBM
product and use of those websites is at your own risk.

© Copyright IBM Corp. 1993, 2014 77

 IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who want to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample

78 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows: © (your company name) (year). Portions of
this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp.
_enter the year or years_.

If you are viewing this information in softcopy, the photographs and color
illustrations may not appear.

Trademarks
IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at http://www.ibm.com/legal/copytrade.shtml.

Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.

Windows is a trademark of Microsoft Corporation in the United States, other

countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Privacy policy considerations

IBM Software products, including software as a service solutions, (“Software
Offerings”) may use cookies or other technologies to collect product usage
information, to help improve the end user experience, to tailor interactions with
the end user or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings
can help enable you to collect personally identifiable information. If this Software
Offering uses cookies to collect personally identifiable information, specific
information about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collect
personally identifiable information.

If the configurations deployed for this Software Offering provide you as customer
the ability to collect personally identifiable information from end users via cookies
and other technologies, you should seek your own legal advice about any laws
applicable to such data collection, including any requirements for notice and
consent.

For more information about the use of various technologies, including cookies, for
these purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy and
IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details the
section entitled “Cookies, Web Beacons and Other Technologies” and the “IBM
Software Products and Software-as-a-Service Privacy Statement” at
http://www.ibm.com/software/info/product-privacy.

Notices 79
80 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages
Glossary
This glossary provides terms and definitions for backup data. See also server storage,
Tivoli Storage Manager, Tivoli Storage FlashCopy storage pool, storage pool volume.
Manager, and associated products.
active file system
A file system to which space management
The following cross-references are used in this
has been added. With space management,
glossary:
tasks for an active file system include
v See refers you from a nonpreferred term to the automatic migration, reconciliation,
preferred term or from an abbreviation to the selective migration, and recall. See also
spelled-out form. inactive file system.
v See also refers you to a related or contrasting
active policy set
term.
The activated policy set that contains the
policy rules currently in use by all client
For other terms and definitions, see the IBM
nodes assigned to the policy domain. See
Terminology website at www.ibm.com/software/
also policy domain, policy set.
globalization/terminology.
active version
The most recent backup copy of a file
A stored. The active version of a file cannot
absolute mode be deleted until a backup process detects
In storage management, a backup that the user has either replaced the file
copy-group mode that specifies that a file with a newer version or has deleted the
is considered for incremental backup even file from the file server or workstation.
if the file has not changed since the last See also backup version, inactive version.
backup. See also mode, modified mode. activity log
access control list (ACL) A log that records normal activity
In computer security, a list associated messages that are generated by the server.
with an object that identifies all the These messages include information about
subjects that can access the object and server and client operations, such as the
their access rights. start time of sessions or device I/O errors.

access mode adaptive subfile backup

An attribute of a storage pool or a storage A type of backup that sends only changed
volume that specifies whether the server portions of a file to the server, instead of
can write to or read from the storage pool sending the entire file. Adaptive subfile
or storage volume. backup reduces network traffic and
increases the speed of the backup.
ACK See acknowledgment.
administrative client
acknowledgment (ACK) A program that runs on a file server,
The transmission of acknowledgment workstation, or mainframe that
characters as a positive response to a data administrators use to control and monitor
transmission. the server. See also backup-archive client.
ACL See access control list. administrative command schedule
activate A database record that describes the
To validate the contents of a policy set planned processing of an administrative
and then make it the active policy set. command during a specific time period.
See also central scheduler, client schedule,
active-data pool schedule.
A named set of storage pool volumes that
contain only active versions of client administrative privilege class
See privilege class.

© Copyright IBM Corp. 1993, 2014 81

administrative session node and a client schedule. An association
A period of time during which an identifies the name of a schedule, the
administrator user ID communicates with name of the policy domain to which the
a server to perform administrative tasks. schedule belongs, and the name of a
See also client node session, session. client node that performs scheduled
operations.
administrator
A person responsible for administrative audit To check for logical inconsistencies
tasks such as access authorization and between information that the server has
content management. Administrators can and the actual condition of the system.
also grant levels of authority to users. The storage manager can audit
information about items such as volumes,
agent node
libraries, and licenses. For example, when
A client node that has been granted proxy
a storage manager audits a volume, the
authority to perform operations on behalf
server checks for inconsistencies between
of another client node, which is the target
information about backed-up or archived
node.
files that are stored in the database and
aggregate the actual data that are associated with
An object, stored in one or more storage each backup version or archive copy in
pools, consisting of a group of logical files server storage.
that are packaged together. See also
authentication rule
logical file, physical file.
A specification that another user can use
aggregate data transfer rate to either restore or retrieve files from
A performance statistic that indicates the storage.
average number of bytes that were
authority
transferred per second while processing a
The right to access objects, resources, or
given operation.
functions. See also privilege class.
application client
authorization rule
A program that is installed on a system to
A specification that permits another user
protect an application. The server
to either restore or retrieve a user's files
provides backup services to an
from storage.
application client.
authorized user
archive
A user who has administrative authority
To copy programs, data, or files to
for the client on a workstation. This user
another storage media, usually for
changes passwords, performs open
long-term storage or security. See also
registrations, and deletes file spaces.
retrieve.
AutoFS
archive copy
See automounted file system.
A file or group of files that was archived
to server storage automatic detection
A feature that detects, reports, and
archive copy group
updates the serial number of a drive or
A policy object containing attributes that
library in the database when the path
control the generation, destination, and
from the local server is defined.
expiration of archived files. See also copy
group. automatic migration
The process that is used to automatically
archive-retention grace period
move files from a local file system to
The number of days that the storage
storage, based on options and settings
manager retains an archived file when the
that are chosen by a root user on a
server is unable to rebind the file to an
workstation. See also demand migration,
appropriate management class. See also
threshold migration.
bind.
automounted file system (AutoFS)
association
A file system that is managed by an
The defined relationship between a client

82 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 automounter daemon. The automounter
daemon monitors a specified directory
path, and automatically mounts the file
system to access data.

B
backup-archive client
A program that runs on a workstation or
file server and provides a means for users
to back up, archive, restore, and retrieve
files. See also administrative client.
backup copy group
A policy object containing attributes that
control the generation, destination, and
expiration of backup versions of files. A
backup copy group belongs to a
management class. See also copy group.
backup retention grace period
The number of days the storage manager
retains a backup version after the server
is unable to rebind the file to an
appropriate management class.
backup set
A portable, consolidated group of active
versions of backup files that are generated
for a backup-archive client.
backup set collection
A group of backup sets that are created at
the same time and which have the same
backup set name, volume names,
description, and device classes. The server
identifies each backup set in the collection
by its node name, backup set name, and
file type.
backup version
A file or directory that a client node
backed up to storage. More than one
backup version can exist in storage, but
only one backup version is the active
version. See also active version, copy
group, inactive version.
bind To associate a file with a management
class name. See also archive-retention
grace period, management class, rebind.

Glossary 83
 the server and used on client nodes in
C conjunction with client options files.
cache To place a duplicate copy of a file on client options file
random access media when the server An editable file that identifies the server
migrates a file to another storage pool in and communication method, and
the hierarchy. provides the configuration for backup,
cache file archive, hierarchical storage management,
A snapshot of a logical volume created by and scheduling.
Logical Volume Snapshot Agent. Blocks client-polling scheduling mode
are saved immediately before they are A method of operation in which the client
modified during the image backup and queries the server for work. See also
their logical extents are saved in the cache server-prompted scheduling mode.
files.
client schedule
CAD See client acceptor daemon. A database record that describes the
central scheduler planned processing of a client operation
A function that permits an administrator during a specific time period. The client
to schedule client operations and operation can be a backup, archive,
administrative commands. The operations restore, or retrieve operation, a client
can be scheduled to occur periodically or operating system command, or a macro.
on a specific date. See also administrative See also administrative command
command schedule, client schedule. schedule, central scheduler, schedule.

client A software program or computer that client/server

requests services from a server. See also Pertaining to the model of interaction in
server. distributed data processing in which a
program on one computer sends a request
client acceptor to a program on another computer and
A service that serves the Java™ applet for awaits a response. The requesting
the web client to web browsers. On program is called a client; the answering
Windows systems, the client acceptor is program is called a server.
installed and run as a service. On AIX,
UNIX, and Linux systems, the client client system-options file
acceptor is run as a daemon. A file, used on AIX, UNIX, or Linux
system clients, containing a set of
client acceptor daemon (CAD) processing options that identify the
See client acceptor. servers to be contacted for services. This
client domain file also specifies communication methods
The set of drives, file systems, or volumes and options for backup, archive,
that the user selects to back up or archive hierarchical storage management, and
data, using the backup-archive client. scheduling. See also client user-options
file, options file.
client node
A file server or workstation on which the client user-options file
backup-archive client program has been A file that contains the set of processing
installed, and which has been registered options that the clients on the system use.
to the server. The set can include options that
determine the server that the client
client node session contacts, and options that affect backup
A session in which a client node operations, archive operations,
communicates with a server to perform hierarchical storage management
backup, restore, archive, retrieve, migrate, operations, and scheduled operations.
or recall requests. See also administrative This file is also called the dsm.opt file.
session. For AIX, UNIX, or Linux systems, see also
client option set client system-options file. See also client
A group of options that are defined on system-options file, options file.

84 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

closed registration copy backup
A registration process in which only an A full backup in which the transaction log
administrator can register workstations as files are not deleted so that backup
client nodes with the server. See also open procedures that use incremental or
registration. differential backups are not disrupted.
collocation copy group
The process of keeping all data belonging A policy object containing attributes that
to a single-client file space, a single client control how backup versions or archive
node, or a group of client nodes on a copies are generated, where backup
minimal number of sequential-access versions or archive copies are initially
volumes within a storage pool. located, and when backup versions or
Collocation can reduce the number of archive copies expire. A copy group
volumes that must be accessed when a belongs to a management class. See also
large amount of data must be restored. archive copy group, backup copy group,
backup version,management class.
collocation group
A user-defined group of client nodes copy storage pool
whose data is stored on a minimal A named set of volumes that contain
number of volumes through the process copies of files that reside in primary
of collocation. storage pools. Copy storage pools are
used only to back up the data that is
commit point
stored in primary storage pools. A copy
A point in time when data is considered
storage pool cannot be a destination for a
to be consistent.
backup copy group, an archive copy
communication method group, or a management class (for
The method by which a client and server space-managed files). See also destination,
exchange information. See also primary storage pool, server storage,
Transmission Control Protocol/Internet storage pool, storage pool volume.
Protocol.
communication protocol D
A set of defined interfaces that permit
computers to communicate with each daemon
other. A program that runs unattended to
perform continuous or periodic functions,
compression such as network control.
A function that removes repetitive
characters, spaces, strings of characters, or damaged file
binary data from the data being processed A physical file in which read errors have
and replaces characters with control been detected.
characters. Compression reduces the database backup series
amount of storage space that is required One full backup of the database, plus up
for data. to 32 incremental backups made since
configuration manager that full backup. Each full backup that is
A server that distributes configuration run starts a new database backup series.
information, such as policies and A number identifies each backup series.
schedules, to managed servers according See also database snapshot, full backup.
to their profiles. Configuration database snapshot
information can include policy and A complete backup of the entire database
schedules. See also enterprise to media that can be taken off-site. When
configuration, managed server, profile. a database snapshot is created, the current
conversation database backup series is not interrupted.
A connection between two programs over A database snapshot cannot have
a session that allows them to incremental database backups associated
communicate with each other while with it. See also database backup series,
processing a transaction. See also session. full backup.

Glossary 85
data center out-of-space condition on a file system for
In a virtualized environment, a container which hierarchical storage management
that holds hosts, clusters, networks, and (HSM) is active. Files are migrated to
data stores. server storage until space usage drops to
the low threshold that was set for the file
data deduplication
system. If the high threshold and low
A method of reducing storage needs by
threshold are the same, one file is
eliminating redundant data. Only one
migrated. See also automatic migration,
instance of the data is retained on storage
selective migration, threshold migration.
media. Other instances of the same data
are replaced with a pointer to the retained desktop client
instance. The group of backup-archive clients that
includes clients on Microsoft Windows,
data manager server
Apple, and Novell NetWare operating
A server that collects metadata
systems.
information for client inventory and
manages transactions for the storage destination
agent over the local area network. The A copy group or management class
data manager server informs the storage attribute that specifies the primary storage
agent with applicable library attributes pool to which a client file will be backed
and the target volume identifier. up, archived, or migrated. See also copy
storage pool.
data mover
A device that moves data on behalf of the device class
server. A network-attached storage (NAS) A named set of characteristics that are
file server is a data mover. applied to a group of storage devices.
Each device class has a unique name and
data storage-management application-
represents a device type of disk, file,
programming interface (DSMAPI)
optical disk, or tape.
A set of functions and semantics that can
monitor events on files, and manage and device configuration file
maintain the data in a file. In an HSM 1. For a storage agent, a file that contains
environment, a DSMAPI uses events to the name and password of the storage
notify data management applications agent, and information about the
about operations on files, stores arbitrary server that is managing the
attribute information with a file, supports SAN-attached libraries and drives that
managed regions in a file, and uses the storage agent uses.
DSMAPI access rights to control access to
2. For a server, a file that contains
a file object.
information about defined device
data store classes, and, on some servers, defined
In a virtualized environment, the location libraries and drives. The information
where virtual machine data is stored. is a copy of the device configuration
information in the database.
deduplication
The process of creating representative disaster recovery manager (DRM)
records from a set of records that have A function that assists in preparing and
been identified as representing the same using a disaster recovery plan file for the
entities. server.
default management class disaster recovery plan
A management class that is assigned to a A file that is created by the disaster
policy set. This class is used to govern recover manager (DRM) that contains
backed up or archived files when a file is information about how to recover
not explicitly associated with a specific computer systems if a disaster occurs and
management class through the scripts that can be run to perform some
include-exclude list. recovery tasks. The file includes
information about the software and
demand migration
The process that is used to respond to an

86 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 hardware that is used by the server, and failure of an operation, a user action, or
the location of recovery media. the change in state of a process. See also
enterprise logging, receiver.
domain
A grouping of client nodes with one or event record
more policy sets, which manage data or A database record that describes actual
storage resources for the client nodes. See status and results for events.
also policy domain.
event server
DRM See disaster recovery manager. A server to which other servers can send
events for logging. The event server
DSMAPI
routes the events to any receivers that are
See data storage-management
enabled for the sending server's events.
application-programming interface.
exabyte (EB)
dynamic serialization
For processor, real and virtual storage
Copy serialization in which a file or
capacities and channel volume, 2 to the
folder is backed up or archived on the
power of 60 or 1 152 921 504 606 846 976
first attempt regardless of whether it
bytes. For disk storage capacity and
changes during a backup or archive. See
communications volume, 1 000 000 000
also shared dynamic serialization, shared
000 000 000 bytes.
static serialization, static serialization.
exclude
The process of identifying files in an
E include-exclude list. This process prevents
EA See extended attribute. the files from being backed up or
migrated whenever a user or schedule
EB See exabyte. enters an incremental or selective backup
EFS See Encrypted File System. operation. A file can be excluded from
backup, from space management, or from
Encrypted File System (EFS) both backup and space management.
A file system that uses file system-level
encryption. exclude-include list
See include-exclude list.
enterprise configuration
A method of setting up servers so that the expiration
administrator can distribute the The process by which files, data sets, or
configuration of one of the servers to the objects are identified for deletion because
other servers, using server-to-server their expiration date or retention period
communication. See also configuration has passed.
manager, managed server, profile, expiring file
subscription. A migrated or premigrated file that has
enterprise logging been marked for expiration and removal
The process of sending events from a from storage. If a stub file or an original
server to a designated event server. The copy of a premigrated file is deleted from
event server routes the events to a local file system, or if the original copy
designated receivers, such as to a user of a premigrated file is updated, the
exit. See also event. corresponding migrated or premigrated
file is marked for expiration the next time
error log reconciliation is run.
A data set or file that is used to record
error information about a product or extend
system. To increase the portion of available space
that can be used to store database or
estimated capacity recovery log information.
The available space, in megabytes, of a
storage pool. extended attribute (EA)
Names or value pairs that are associated
event An occurrence of significance to a task or with files or directories. There are three
system. Events can include completion or

Glossary 87
 classes of extended attributes: user management support that is required. If
attributes, system attributes, and trusted no space management support is
attributes. required, the operation is passed to the
operating system, which performs its
external library
normal functions. The file system
A collection of drives that is managed by
migrator is mounted over a file system
the media-management system other than
when space management is added to the
the storage management server.
file system.
file system state
F The storage management mode of a file
file access time system that resides on a workstation on
On AIX, UNIX, or Linux systems, the which the hierarchical storage
time when the file was last accessed. management (HSM) client is installed. A
file system can be in one of these states:
file age native, active, inactive, or global inactive.
For migration prioritization purposes, the
number of days since a file was last frequency
accessed. A copy group attribute that specifies the
minimum interval, in days, between
file device type incremental backups.
A device type that specifies the use of
sequential access files on disk storage as FSID See file space ID.
volumes. FSM See file system migrator.
file server full backup
A dedicated computer and its peripheral The process of backing up the entire
storage devices that are connected to a server database. A full backup begins a
local area network that stores programs new database backup series. See also
and files that are shared by users on the database backup series, database
network. snapshot, incremental backup.
file space fuzzy backup
A logical space in server storage that A backup version of a file that might not
contains a group of files that have been accurately reflect what is currently in the
backed up or archived by a client node, file because the file was backed up at the
from a single logical partition, file system, same time as it was being modified.
or virtual mount point. Client nodes can
restore, retrieve, or delete their file spaces fuzzy copy
from server storage. In server storage, A backup version or archive copy of a file
files belonging to a single file space are that might not accurately reflect the
not necessarily stored together. original contents of the file because it was
backed up or archived the file while the
file space ID (FSID) file was being modified.
A unique numeric identifier that the
server assigns to a file space when it is
stored in server storage. G
file state GB See gigabyte.
The space management mode of a file
General Parallel File System (GPFS™)
that resides in a file system to which
A high-performance shared-disk file
space management has been added. A file
system that can provide data access from
can be in one of three states: resident,
nodes in a clustered system environment.
premigrated, or migrated. See also
See also information lifecycle
migrated file, premigrated file, resident
management.
file.
gigabyte (GB)
file system migrator (FSM)
For processor storage, real and virtual
A kernel extension that intercepts all file
storage, and channel volume, 10 to the
system operations and provides any space

88 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 power of nine or 1,073,741,824 bytes. For
disk storage capacity and communications
volume, 1,000,000,000 bytes.
global inactive state
The state of all file systems to which
space management has been added when
space management is globally deactivated
for a client node.
Globally Unique Identifier (GUID)
An algorithmically determined number
that uniquely identifies an entity within a
system. See also Universally Unique
Identifier.
GPFS See General Parallel File System.
GPFS node set
A mounted, defined group of GPFS file
systems.
group backup
The backup of a group containing a list of
files from one or more file space origins.
GUID See Globally Unique Identifier.

H
hierarchical storage management (HSM)
A function that automatically distributes
and manages data on disk, tape, or both
by regarding devices of these types and
potentially others as levels in a storage
hierarchy that range from fast, expensive
devices to slower, cheaper, and possibly
removable devices. The objectives are to
minimize access time to data and
maximize available media capacity. See
also hierarchical storage management
client, recall, storage hierarchy.
hierarchical storage management client (HSM
client) A client program that works with the
server to provide hierarchical storage
management (HSM) for a system. See also
hierarchical storage management,
management class.
HSM See hierarchical storage management.
HSM client
See hierarchical storage management
client.

Glossary 89
 systems. An inode contains the node,
I type, owner, and location of a file.
ILM See information lifecycle management. inode number
image A file system or raw logical volume that A number specifying a particular inode
is backed up as a single object. file in the file system.
image backup IP address
A backup of a full file system or raw A unique address for a device or logical
logical volume as a single object. unit on a network that uses the Internet
Protocol standard.
inactive file system
A file system for which space
management has been deactivated. See J
also active file system.
job file
inactive version A generated file that contains
A backup version of a file that is either configuration information for a migration
not the most recent backup version, or job. The file is XML format and can be
that is a backup version of a file that no created and edited in the hierarchical
longer exists on the client system. Inactive storage management (HSM) client for
backup versions are eligible for expiration Windows client graphical user interface.
processing according to the management See also migration job.
class assigned to the file. See also active
journal-based backup
version, backup version.
A method for backing up Windows clients
include-exclude file and AIX clients that exploits the change
A file containing statements to determine notification mechanism in a file to
the files to back up and the associated improve incremental backup performance
management classes to use for backup or by reducing the need to fully scan the file
archive. See also include-exclude list. system.
include-exclude list journal daemon
A list of options that include or exclude On AIX, UNIX, or Linux systems, a
selected files for backup. An exclude program that tracks change activity for
option identifies files that should not be files residing in file systems.
backed up. An include option identifies
journal service
files that are exempt from the exclusion
In Microsoft Windows, a program that
rules or assigns a management class to a
tracks change activity for files residing in
file or a group of files for backup or
file systems.
archive services. See also include-exclude
file.
incremental backup
K
The process of backing up files or KB See kilobyte.
directories, or copying pages in the
database, that are new or changed since kilobyte (KB)
the last full or incremental backup. See For processor storage, real and virtual
also selective backup. storage, and channel volume, 2 to the
power of 10 or 1,024 bytes. For disk
individual mailbox restore storage capacity and communications
See mailbox restore. volume, 1,000 bytes.
information lifecycle management (ILM)
A policy-based file-management system
for storage pools and file sets. See also
General Parallel File System.
inode The internal structure that describes the
individual files on AIX, UNIX, or Linux

90 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 local shadow volume
L Data that is stored on shadow volumes
LAN See local area network. localized to a disk storage subsystem.
LAN-free data movement LOFS See loopback virtual file system.
The movement of client data between a logical file
client system and a storage device on a A file that is stored in one or more server
storage area network (SAN), bypassing storage pools, either by itself or as part of
the local area network. an aggregate. See also aggregate, physical
LAN-free data transfer file, physical occupancy.
See LAN-free data movement. logical occupancy
leader data The space that is used by logical files in a
Bytes of data, from the beginning of a storage pool. This space does not include
migrated file, that are stored in the file's the unused space created when logical
corresponding stub file on the local file files are deleted from aggregate files, so it
system. The amount of leader data that is might be less than the physical
stored in a stub file depends on the stub occupancy. See also physical occupancy.
size that is specified. logical unit number (LUN)
library In the Small Computer System Interface
1. A repository for demountable (SCSI) standard, a unique identifier used
recorded media, such as magnetic to differentiate devices, each of which is a
disks and magnetic tapes. logical unit (LU).
2. A collection of one or more drives, logical volume
and possibly robotic devices A portion of a physical volume that
(depending on the library type), which contains a file system.
can be used to access storage volumes. logical volume backup
library client A back up of a file system or logical
A server that uses server-to-server volume as a single object.
communication to access a library that is Logical Volume Snapshot Agent (LVSA)
managed by another storage management Software that can act as the snapshot
server. See also library manager. provider for creating a snapshot of a
library manager logical volume during an online image
A server that controls device operations backup.
when multiple storage management loopback virtual file system (LOFS)
servers share a storage device. See also A file system that is created by mounting
library client. a directory over another local directory,
local also known as mount-over-mount. A
1. Pertaining to a device, file, or system LOFS can also be generated using an
that is accessed directly from a user automounter.
system, without the use of a LUN See logical unit number.
communication line. See also remote.
LVSA See Logical Volume Snapshot Agent.
2. For hierarchical storage management
products, pertaining to the destination
of migrated files that are being
moved. See also remote.
local area network (LAN)
A network that connects several devices
in a limited area (such as a single
building or campus) and that can be
connected to a larger network.

Glossary 91
 storage for Tivoli Storage Manager servers
M that run on operating systems other than
macro file z/OS.
A file that contains one or more storage megabyte (MB)
manager administrative commands, For processor storage, real and virtual
which can be run only from an storage, and channel volume, 2 to the
administrative client using the MACRO 20th power or 1,048,576 bytes. For disk
command. See also Tivoli Storage storage capacity and communications
Manager command script. volume, 1,000,000 bytes.
mailbox restore metadata
A function that restores Microsoft Data that describes the characteristics of
Exchange Server data (from IBM Data data; descriptive data.
Protection for Microsoft Exchange
backups) at the mailbox level or migrate
mailbox-item level. To move data to another location, or an
application to another computer system.
managed object
A definition in the database of a managed migrated file
server that was distributed to the A file that has been copied from a local
managed server by a configuration file system to storage. For HSM clients on
manager. When a managed server UNIX or Linux systems, the file is
subscribes to a profile, all objects that are replaced with a stub file on the local file
associated with that profile become system. On Windows systems, creation of
managed objects in the database of the the stub file is optional. See also file state,
managed server. premigrated file, resident file, stub file.

managed server migration

A server that receives configuration The process of moving data from one
information from a configuration manager computer system to another, or an
using a subscription to one or more application to another computer system.
profiles. Configuration information can migration job
include definitions of objects such as A specification of files to migrate, and
policy and schedules. See also actions to perform on the original files
configuration manager, enterprise after migration. See also job file, threshold
configuration, profile, subscription. migration.
management class migration threshold
A policy object that users can bind to each High and low capacities for storage pools
file to specify how the server manages the or file systems, expressed as percentages,
file. The management class can contain a at which migration is set to start and
backup copy group, an archive copy stop.
group, and space management attributes.
See also bind, copy group, hierarchical mirroring
storage management client, policy set, The process of writing the same data to
rebind. multiple disks at the same time. The
mirroring of data protects it against data
maximum transmission unit (MTU) loss within the database or within the
The largest possible unit of data that can recovery log.
be sent on a given physical medium in a
single frame. For example, the maximum mode A copy group attribute that specifies
transmission unit for Ethernet is 1500 whether to back up a file that has not
bytes. been modified since the last time the file
was backed up. See also absolute mode,
MB See megabyte. modified mode.
media server modified mode
In a z/OS® environment, a program that In storage management, a backup
provides access to z/OS disk and tape copy-group mode that specifies that a file

92 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 is considered for incremental backup only storage (NAS) file server. Data for the
if it has changed since the last backup. A NAS node is transferred by a NAS file
file is considered a changed file if the server that is controlled by the network
date, size, owner, or permissions of the data management protocol (NDMP). A
file have changed. See also absolute NAS node is also called a NAS file server
mode, mode. node.
mount limit native file system
The maximum number of volumes that A file system that is locally added to the
can be simultaneously accessed from the file server and is not added for space
same device class. The mount limit management. The hierarchical storage
determines the maximum number of manager (HSM) client does not provide
mount points. See also mount point. space management services to the file
system.
mount point
A logical drive through which volumes native format
are accessed in a sequential access device A format of data that is written to a
class. For removable media device types, storage pool directly by the server. See
such as tape, a mount point is a logical also non-native data format.
drive associated with a physical drive. For
NDMP
the file device type, a mount point is a
See Network Data Management Protocol.
logical drive associated with an I/O
stream. See also mount limit. NetBIOS (Network Basic Input/Output System)
A standard interface to networks and
mount retention period
personal computers that is used on local
The maximum number of minutes that
area networks to provide message,
the server retains a mounted
print-server, and file-server functions.
sequential-access media volume that is
Application programs that use NetBIOS
not being used before it dismounts the
do not have to handle the details of LAN
sequential-access media volume.
data link control (DLC) protocols.
mount wait period
network-attached storage file server (NAS file
The maximum number of minutes that
server)
the server waits for a sequential-access
A dedicated storage device with an
volume mount request to be satisfied
operating system that is optimized for
before canceling the request.
file-serving functions. A NAS file server
MTU See maximum transmission unit. can have the characteristics of both a
node and a data mover.
N Network Basic Input/Output System
See NetBIOS.
Nagle algorithm
An algorithm that reduces congestion of Network Data Management Protocol (NDMP)
TCP/IP networks by combining smaller A protocol that allows a network
packets and sending them together. storage-management application to
control the backup and recovery of an
named pipe NDMP-compliant file server, without
A type of interprocess communication installing vendor-acquired software on
that permits message data streams to pass that file server.
between peer processes, such as between
a client and a server. network data-transfer rate
A rate that is calculated by dividing the
NAS file server total number of bytes that are transferred
See network-attached storage file server. by the data transfer time. For example,
NAS file server node this rate can be the time that is spent
See NAS node. transferring data over a network.
NAS node node A file server or workstation on which the
A client node that is a network-attached

Glossary 93
 backup-archive client program has been contacting for space management services.
installed, and which has been registered For example, a stub file can be orphaned
to the server. when the client system-options file is
modified to contact a server that is
node name
different than the one to which the file
A unique name that is used to identify a
was migrated.
workstation, file server, or PC to the
server.
node privilege class
P
A privilege class that gives an packet In data communication, a sequence of
administrator the authority to remotely binary digits, including data and control
access backup-archive clients for a specific signals, that are transmitted and switched
client node or for all clients in a policy as a composite whole.
domain. See also privilege class.
page A defined unit of space on a storage
non-native data format medium or within a database volume.
A format of data that is written to a
storage pool that differs from the format partial-file recall mode
that the server uses for operations. See A recall mode that causes the hierarchical
also native format. storage management (HSM) function to
read just a portion of a migrated file from
storage, as requested by the application
O accessing the file.
offline volume backup password generation
A backup in which the volume is locked A process that creates and stores a new
so that no other system applications can password in an encrypted password file
access it during the backup operation. when the old password expires.
Automatic generation of a password
online volume backup
prevents password prompting.
A backup in which the volume is
available to other system applications path An object that defines a one-to-one
during the backup operation. relationship between a source and a
destination. Using the path, the source
open registration
accesses the destination. Data can flow
A registration process in which users can
from the source to the destination, and
register their workstations as client nodes
back. An example of a source is a data
with the server. See also closed
mover (such as a network-attached
registration.
storage [NAS] file server), and an
operator privilege class example of a destination is a tape drive.
A privilege class that gives an
pattern-matching character
administrator the authority to disable or
See wildcard character.
halt the server, enable the server, cancel
server processes, and manage removable physical file
media. See also privilege class. A file that is stored in one or more
storage pools, consisting of either a single
options file
logical file, or a group of logical files that
A file that contains processing options.
are packaged together as an aggregate.
See also client system-options file, client
See also aggregate, logical file, physical
user-options file.
occupancy.
originating file system
physical occupancy
The file system from which a file was
The amount of space that is used by
migrated. When a file is recalled, it is
physical files in a storage pool. This space
returned to its originating file system.
includes the unused space that is created
orphaned stub file when logical files are deleted from
A file for which no migrated file can be aggregates. See also logical file, logical
found on the server that the client node is occupancy, physical file.

94 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

plug-in primary storage pool
A separately installable software module A named set of volumes that the server
that adds function to an existing program, uses to store backup versions of files,
application, or interface. archive copies of files, and files migrated
from client nodes. See also copy storage
policy domain
pool, server storage, storage pool, storage
A grouping of policy users with one or
pool volume.
more policy sets, which manage data or
storage resources for the users. The users privilege class
are client nodes that are associated with A level of authority that is granted to an
the policy domain. See also active policy administrator. The privilege class
set, domain. determines which administrative tasks the
administrator can perform. See also
policy privilege class
authority, node privilege class, operator
A privilege class that gives an
privilege class, policy privilege class,
administrator the authority to manage
storage privilege class, system privilege
policy objects, register client nodes, and
class.
schedule client operations for client
nodes. Authority can be restricted to profile
certain policy domains. See also privilege A named group of configuration
class. information that can be distributed from a
configuration manager when a managed
policy set
server subscribes. Configuration
A group of rules in a policy domain. The
information can include registered
rules specify how data or storage
administrator IDs, policies, client
resources are automatically managed for
schedules, client option sets,
client nodes in the policy domain. Rules
administrative schedules, storage manager
can be contained in management classes.
command scripts, server definitions, and
See also active policy set, management
server group definitions. See also
class.
configuration manager, enterprise
premigrated file configuration, managed server.
A file that has been copied to server
profile association
storage, but has not been replaced with a
On a configuration manager, the defined
stub file on the local file system. An
relationship between a profile and an
identical copy of the file resides both on
object such as a policy domain. Profile
the local file system and in server storage.
associations define the configuration
Premigrated files occur on UNIX and
information that is distributed to a
Linux file systems to which space
managed server when it subscribes to the
management has been added. See also file
profile.
state, migrated file, resident file.
premigrated files database
A database that contains information
Q
about each file that has been premigrated quota
to server storage. 1. For HSM on AIX, UNIX, or Linux
premigration systems, the limit (in megabytes) on
The process of copying files that are the amount of data that can be
eligible for migration to server storage, migrated and premigrated from a file
but leaving the original file intact on the system to server storage.
local file system. 2. For HSM on Windows systems, a
premigration percentage user-defined limit to the space that is
A space management setting that controls occupied by recalled files.
whether the next eligible candidates in a
file system are premigrated following
threshold or demand migration.

Glossary 95
 During the reconciliation process, data
R that is identified as no longer needed is
randomization removed.
The process of distributing schedule start recovery log
times for different clients within a A log of updates that are about to be
specified percentage of the schedule's written to the database. The log can be
startup window. used to recover from system and media
raw logical volume failures. The recovery log consists of the
A portion of a physical volume that is active log (including the log mirror) and
comprised of unallocated blocks and has archive logs.
no journaled file system (JFS) definition. register
A logical volume is read/write accessible To define a client node or administrator
only through low-level I/O functions. ID that can access the server.
rebind registry
To associate all backed-up versions of a A repository that contains access and
file with a new management class name. configuration information for users,
For example, a file that has an active systems, and software.
backup version is rebound when a later
version of the file is backed up with a remote
different management class association. For hierarchical storage management
See also bind, management class. products, pertaining to the origin of
migrated files that are being moved. See
recall To copy a migrated file from server also local.
storage back to its originating file system
using the hierarchical storage resident file
management client. See also selective On a Windows system, a complete file on
recall. a local file system that might also be a
migrated file because a migrated copy can
receiver exist in server storage. On a UNIX or
A server repository that contains a log of Linux system, a complete file on a local
server and client messages as events. For file system that has not been migrated or
example, a receiver can be a file exit, a premigrated, or that has been recalled
user exit, or the server console and from server storage and modified. See
activity log. See also event. also file state.
reclamation restore
The process of consolidating the To copy information from its backup
remaining data from many location to the active storage location for
sequential-access volumes onto fewer, use. For example, to copy information
new sequential-access volumes. from server storage to a client
reclamation threshold workstation.
The percentage of space that a retention
sequential-access media volume must The amount of time, in days, that inactive
have before the server can reclaim the backed-up or archived files are kept in the
volume. Space becomes reclaimable when storage pool before they are deleted.
files are expired or are deleted. Copy group attributes and default
reconciliation retention grace periods for the domain
The process of ensuring consistency define retention.
between the original data repository and retrieve
the larger system where the data is stored To copy archived information from the
for backup. Examples of larger systems storage pool to the workstation for use.
where the data is stored for backup are The retrieve operation does not affect the
storage servers or other storage systems. archive version in the storage pool. See
also archive.

96 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

root user selective recall
A system user who operates without The process of copying user-selected files
restrictions. A root user has the special from server storage to a local file system.
rights and privileges needed to perform See also recall, transparent recall.
administrative tasks.
serialization
The process of handling files that are
S modified during backup or archive
processing. See also shared dynamic
SAN See storage area network. serialization, shared static serialization,
schedule static serialization.
A database record that describes client server A software program or a computer that
operations or administrative commands to provides services to other software
be processed. See also administrative programs or other computers. See also
command schedule, client schedule. client.
scheduling mode server options file
The type of scheduling operation for the A file that contains settings that control
server and client node that supports two various server operations. These settings
scheduling modes: client-polling and affect such things as communications,
server-prompted. devices, and performance.
scratch volume server-prompted scheduling mode
A labeled volume that is either blank or A client/server communication technique
contains no valid data, that is not defined, where the server contacts the client node
and that is available for use. See also when tasks must be done. See also
volume. client-polling scheduling mode.
script A series of commands, combined in a file, server storage
that carry out a particular function when The primary, copy, and active-data storage
the file is run. Scripts are interpreted as pools that are used by the server to store
they are run. See also Tivoli Storage user files such as backup versions, archive
Manager command script. copies, and files migrated from
Secure Sockets Layer (SSL) hierarchical storage management client
A security protocol that provides nodes (space-managed files). See also
communication privacy. With SSL, active-data pool, copy storage pool,
client/server applications can primary storage pool, storage pool
communicate in a way that is designed to volume, volume.
prevent eavesdropping, tampering, and session
message forgery. A logical or virtual connection between
selective backup two stations, software programs, or
The process of backing up certain files or devices on a network that allows the two
directories from a client domain. The files elements to communicate and exchange
that are backed up are those that are not data for the duration of the session. See
excluded in the include-exclude list. The also administrative session.
files must meet the requirement for session resource usage
serialization in the backup copy group of The amount of wait time, processor time,
the management class that is assigned to and space that is used or retrieved during
each file. See also incremental backup. a client session.
selective migration shadow copy
The process of copying user-selected files A snapshot of a volume. The snapshot
from a local file system to server storage can be taken while applications on the
and replacing the files with stub files on system continue to write data to the
the local file system. See also demand volumes.
migration, threshold migration.

Glossary 97
shadow volume special file
The data stored from a snapshot of a On AIX, UNIX, or Linux systems, a file
volume. The snapshot can be taken while that defines devices for the system, or
applications on the system continue to temporary files that are created by
write data to the volumes. processes. There are three basic types of
special files: first-in, first-out (FIFO);
shared dynamic serialization
block; and character.
A value for serialization that specifies that
a file must not be backed up or archived SSL See Secure Sockets Layer.
if it is being modified during the
stabilized file space
operation. The backup-archive client
A file space that exists on the server but
retries the backup or archive operation a
not on the client.
number of times; if the file is being
modified during each attempt, the stanza A group of lines in a file that together
backup-archive client will back up or have a common function or define a part
archive the file on its last try. See also of the system. Stanzas are usually
dynamic serialization, serialization, shared separated by blank lines or colons, and
static serialization, static serialization. each stanza has a name.
shared library startup window
A library device that is used by multiple A time period during which a schedule
storage manager servers. See also library. must be initiated.
shared static serialization static serialization
A copy-group serialization value that A copy-group serialization value that
specifies that a file must not be modified specifies that a file must not be modified
during a backup or archive operation. The during a backup or archive operation. If
client attempts to retry the operation a the file is in use during the first attempt,
number of times. If the file is in use the backup-archive client cannot back up
during each attempt, the file is not backed or archive the file. See also dynamic
up or archived. See also dynamic serialization, serialization, shared dynamic
serialization, serialization, shared dynamic serialization, shared static serialization.
serialization, static serialization.
storage agent
snapshot A program that enables the backup and
An image backup type that consists of a restoration of client data directly to and
point-in-time view of a volume. from storage attached to a storage area
network (SAN).
space-managed file
A file that is migrated from a client node storage area network (SAN)
by the hierarchical storage management A dedicated storage network tailored to a
(HSM) client. The HSM client recalls the specific environment, combining servers,
file to the client node on demand. systems, storage products, networking
products, software, and services.
space management
See hierarchical storage management. storage hierarchy
A logical order of primary storage pools,
space monitor daemon
as defined by an administrator. The order
A daemon that checks space usage on all
is typically based on the speed and
file systems for which space management
capacity of the devices that the storage
is active, and automatically starts
pools use. The storage hierarchy is
threshold migration when space usage on
defined by identifying the next storage
a file system equals or exceeds its high
pool in a storage pool definition. See also
threshold.
storage pool.
sparse file
storage pool
A file that is created with a length greater
A named set of storage volumes that is
than the data it contains, leaving empty
the destination that is used to store client
spaces for the future addition of data.

98 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages

 data. See also active-data pool, copy
storage pool, primary storage pool,
storage hierarchy.
storage pool volume
A volume that has been assigned to a
storage pool. See also active-data pool,
copy storage pool, primary storage pool,
server storage, volume.
storage privilege class
A privilege class that gives an
administrator the authority to control how
storage resources for the server are
allocated and used, such as monitoring
the database, the recovery log, and server
storage. See also privilege class.
stub A shortcut on the Windows file system
that is generated by the hierarchical
storage management (HSM) client for a
migrated file that allows transparent user
access. A stub is the sparse file
representation of a migrated file, with a
reparse point attached.
stub file
A file that replaces the original file on a
local file system when the file is migrated
to storage. A stub file contains the
information that is necessary to recall a
migrated file from server storage. It also
contains additional information that can
be used to eliminate the need to recall a
migrated file. See also migrated file,
resident file.
stub file size
The size of a file that replaces the original
file on a local file system when the file is
migrated to server storage. The size that
is specified for stub files determines how
much leader data can be stored in the
stub file. The default for stub file size is
the block size defined for a file system
minus 1 byte.
subscription
In a storage environment, the process of
identifying the subscribers to which the
profiles are distributed. See also
enterprise configuration, managed server.
system privilege class
A privilege class that gives an
administrator the authority to issue all
server commands. See also privilege class.

Glossary 99
 tombstone object
T A small subset of attributes of a deleted
tape library object. The tombstone object is retained
A set of equipment and facilities that for a specified period, and at the end of
support an installation's tape the specified period, the tombstone object
environment. The tape library can include is permanently deleted.
tape storage racks, mechanisms for Transmission Control Protocol/Internet Protocol
automatic tape mounting, a set of tape (TCP/IP)
drives, and a set of related tape volumes An industry-standard, nonproprietary set
mounted on those drives. of communication protocols that provides
tape volume prefix reliable end-to-end connections between
The high-level-qualifier of the file name applications over interconnected networks
or the data set name in the standard tape of different types. See also communication
label. method.
target node transparent recall
A client node for which other client nodes The process that is used to automatically
(called agent nodes) have been granted recall a migrated file to a workstation or
proxy authority. The proxy authority file server when the file is accessed. See
allows the agent nodes to perform also selective recall.
operations such as backup and restore on trusted communications agent (TCA)
behalf of the target node, which owns the A program that handles the sign-on
data. password protocol when clients use
TCA See trusted communications agent. password generation.
TCP/IP
See Transmission Control U
Protocol/Internet Protocol.
UCS-2 A 2-byte (16-bit) encoding scheme based
threshold migration on ISO/IEC specification 10646-1. UCS-2
The process of moving files from a local defines three levels of implementation:
file system to server storage based on the Level 1-No combining of encoded
high and low thresholds that are defined elements allowed; Level 2-Combining of
for the file system. See also automatic encoded elements is allowed only for
migration, demand migration, migration Thai, Indic, Hebrew, and Arabic; Level
job, selective migration. 3-Any combination of encoded elements
are allowed.
throughput
In storage management, the total bytes in UNC See Universal Naming Convention.
the workload, excluding overhead, that
Unicode
are backed up or restored, divided by
A character encoding standard that
elapsed time.
supports the interchange, processing, and
timeout display of text that is written in the
A time interval that is allotted for an common languages around the world,
event to occur or complete before plus many classical and historical texts.
operation is interrupted.
Unicode-enabled file space
Tivoli Storage Manager command script Unicode file space names provide support
A sequence of Tivoli Storage Manager for multilingual workstations without
administrative commands that are stored regard for the current locale.
in the database of the Tivoli Storage
Universally Unique Identifier (UUID)
Manager server. The script can run from
The 128-bit numeric identifier that is used
any interface to the server. The script can
to ensure that two components do not
include substitution for command
have the same identifier. See also Globally
parameters and conditional logic. See also
Unique Identifier.
macro file, script.

100 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages
Universal Naming Convention (UNC) volume history file
The server name and network name A file that contains information about
combined. These names together identify volumes that have been used by the
the resource on the domain. server for database backups and for
export of administrator, node, policy, or
UTF-8 Unicode Transformation Format, 8-bit
server data. The file also has information
encoding form, which is designed for ease
about sequential-access storage pool
of use with existing ASCII-based systems.
volumes that have been added, reused, or
The CCSID value for data in UTF-8
deleted. The information is a copy of
format is 1208. See also UCS-2.
volume information that is recorded in
UUID See Universally Unique Identifier. the server database.
Volume Shadow Copy Service (VSS)
V A set of Microsoft application-
programming interfaces (APIs) that are
validate used to create shadow copy backups of
To check a policy set for conditions that volumes, exact copies of files, including
can cause problems if that policy set all open files, and so on.
becomes the active policy set. For
example, the validation process checks VSS See Volume Shadow Copy Service.
whether the policy set contains a default VSS Backup
management class. A backup operation that uses Microsoft
version Volume Shadow Copy Service (VSS)
A backup copy of a file stored in server technology. The backup operation
storage. The most recent backup copy of a produces an online snapshot
file is the active version. Earlier copies of (point-in-time consistent copy) of
the same file are inactive versions. The Microsoft Exchange data. This copy can
number of versions retained by the server be stored on local shadow volumes or on
is determined by the copy group Tivoli Storage Manager server storage.
attributes in the management class. VSS Fast Restore
virtual file space An operation that restores data from a
A representation of a directory on a local snapshot. The snapshot is the VSS
network-attached storage (NAS) file backup that resides on a local shadow
system as a path to that directory. volume. The restore operation retrieves
the data by using a file-level copy
virtual mount point method.
A directory branch of a file system that is
defined as a virtual file system. The VSS Instant Restore
virtual file system is backed up to its own An operation that restores data from a
file space on the server. The server local snapshot. The snapshot is the VSS
processes the virtual mount point as a backup that resides on a local shadow
separate file system, but the client volume. The restore operation retrieves
operating system does not. the data by using a hardware assisted
restore method (for example, a FlashCopy
virtual volume operation).
An archive file on a target server that
represents a sequential media volume to a VSS offloaded backup
source server. A backup operation that uses a Microsoft
Volume Shadow Copy Service (VSS)
volume hardware provider (installed on an
A discrete unit of storage on disk, tape or alternate system) to move IBM Data
other data recording medium that Protection for Microsoft Exchange data to
supports some form of identifier and the Tivoli Storage Manager server. This
parameter list, such as a volume label or type of backup operation shifts the
input/output control. See also scratch backup load from the production system
volume, server storage, storage pool, to another system.
storage pool volume.

Glossary 101
VSS Restore
A function that uses a Microsoft Volume
Shadow Copy Service (VSS) software
provider to restore VSS Backups (IBM
Data Protection for Microsoft Exchange
database files and log files) that reside on
Tivoli Storage Manager server storage to
their original location.

102 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages
 workstation
W A terminal or personal computer at which
wildcard character a user can run applications and that is
A special character such as an asterisk (*) usually connected to a mainframe or a
or a question mark (?) that can be used to network.
represent one or more characters. Any worldwide name (WWN)
character or set of characters can replace A 64-bit, unsigned name identifier that is
the wildcard character. unique.
workload partition (WPAR) WPAR See workload partition.
A partition within a single operating
system instance. WWN See worldwide name.

Glossary 103
104 IBM Tivoli Storage Manager for Enterprise Resource Planning: Messages



Product Number: 5608-E05

Printed in USA