FMM common messages

FMM messages in the range 0000-9999 are common messages. Common messages are issued by the following IBM® Tivoli® Storage FlashCopy® Manager components:

Tivoli Storage FlashCopy Manager for UNIX and Linux
Tivoli Storage FlashCopy Manager for VMware

Tivoli Storage FlashCopy Manager common messages are listed in ascending numeric order. The complete message is documented, including message ID, message text, explanation, system action, and user response.

FMM0001E
Profile not specified.
FMM0004E
Function not defined. [ function ]
FMM0005I
Start of program at: time.
FMM0006E
Type for backup not defined [ type ]. Please use 'file' or 'file_online'.
FMM0007E
Mode mode requires the environment variable environment variables to be set.
FMM0008E
The environment variable name is not set correctly. The current value is "value".
FMM0009E
The option 'option' must be specified after the '-t FAKE' option. This is true for all fake relevant options.
FMM0010E
The option 'option' contains an invalid argument
FMM0011E
Semantic errors were detected in the fake definition: 'definition'
FMM0012I
command: 'command'
FMM0020I
End of program at: time.
FMM0021I
Elapsed time: elapsed time.
FMM0023I
Time: current time Done: saved bytes (percent) of bytes. Estimated end time: end time.
FMM0024I
Return code is: return code.
FMM0027I
Time: current time Object: current number of total number in process: file_name Size: size, management class: management class, server: server name .
FMM0032E
Error opening file file name: system error description
FMM0048E
No password for node node name on server server name given on command line.When entering passwords in batch mode, you must supply values for all stanzas in the profile.
FMM0049I
Enter the password for node node name on server server name:
FMM0050I
Enter password for node node name on server server name again:
FMM0051I
Password successfully verified for node node name on server server name.
FMM0052E
Password verification for node node name on server server name failed.
FMM0053I
Time: current time Object: current number of total number complete: file name with: bytes saved with description object description.
FMM0054I
Time: current time Object: current num of total num complete: file name with: bytes restored with description object description .
FMM0055I
Object object name with size saved with description description.
FMM0056I
Object object name with size restored with description description.
FMM0057I
Time: current time Object: object name with: size saved with description description.
FMM0058I
Time: current time Object: object name with: size restored with description description.
FMM0059E
Data Protection for SAP cannot find the client options file.
FMM0060E
The command parameter parameter is not recognized.
FMM0061W
The output file file name is not valid.
FMM0062E
The input file filename is not valid.
FMM0063E
The UTL file file name is not valid.
FMM0064E
The option 'option' is not recognized.
FMM0065E
The argument is missing for option 'option'.
FMM0101I
Enter 'cont' to continue or 'stop' to cancel.
FMM0102I
Your reply: 'reply'.
FMM0104I
Deleting the data container 'dcid' from the backup 'snapid' in the repository. IBM Tivoli Storage FlashCopy(R) Manager found that the volumes of this data container do not contain a valid snapshot in the storage system.
FMM0105I
If the newest FlashCopy targets of the mirror copy sources are space efficient volumes, then they will grow up to the size of the sources.
FMM0106I
The newest snapshot of the mirror copy will grow up to the size of the sources.
FMM0122I
Backup ID: backup identifier
FMM0123E
Option -i <backup_list> not specified.
FMM0124E
The LUN 'LUN name' on the datastore 'datastorename' is not part of a storage subsystem supported by IBM Tivoli Storage FlashCopy(R) Manager.
FMM0127E
The backup corresponding to this consistency group cg cannot be deleted as it is not the oldest in the cascade of dependent flashcopy maps.
FMM0128E
The 'disk names' virtual disk(s) of the virtual machine 'VM name' have a disk type which is not supported by IBM Tivoli Storage FlashCopy(R) Manager. The virtual machine is not included in the backup.
FMM0129E
The following error was returned by the vSphere(TM) API: 'vSphere error'.
FMM0136I
Start of the reconciliation between the IBM Tivoli Storage FlashCopy(R) Manager repository and the storage system.
FMM0137I
End of the reconciliation.
FMM0138I
Time stamp: current_time.
FMM0142I
Snapshot started ...
FMM0143I
Snapshot successful.
FMM0144W
Information from DP for mySAP was not found.
FMM0147I
The IDS control file exists and a new backup cycle entry has been created.
FMM0148E
The backup ID was not passed by DP for mySAP. This snapshot backup cannot be used for snapshot restore.
FMM0149E
The IDS control file is corrupt!
FMM0150I
The IDS control file 'ids_control_file' does not exist, it will be created.
FMM0151E
The IDS control file has no entry.
FMM0152E
The IDS control file must be read or inserted before update.
FMM0153W
The value of the field 'field_name' in the file 'file_name' is empty.
FMM0154W
Info data from DP for mySAP /tmp/bki<SID>.ids cannot be read.
FMM0155I
The maximum number of backup cycles in the IDS control file has been reached.
FMM0156I
Delete backup cycle with BSEQ_N = beseq_n and all the associated files ...
FMM0157W
Directory Path 'directory' for the report files does not exist. Using the current directory.
FMM0158I
Start of listing of importing volume groups/mounting file systems ...
FMM0159I
End of listing.
FMM0160I
The unmount process will be skipped because the progress status indicator (PSI) has a value of 'psi'.
FMM0162E
The version of the splitint program must be the same on the backup and production system.
FMM0163I
Enter the password for the user 'user ID' :
FMM0164I
Enter the password for the user 'user ID' again:
FMM0165I
The password entry does not match, please try again.
FMM0166E
No password stored.
FMM0167E
The config file named 'config_file' could not be opened. Please call 'splitint' with the function 'password' to create this file.
FMM0172I
Start of listing of exported volume groups/unmounting file systems ...
FMM0173I
Start of withdraw of the target-source pairs ...
FMM0177E
You cannot run the function 'function' if the progress status indicator (PSI) has a value of 'psi'.
FMM0182E
The option -f flashback can only be used on the production system.
FMM0183E
Topic named 'topicname' could not be found in the file 'filename'.
FMM0184E
The source volume <serial number> cannot be specified as a target volume in the .fct file.
FMM0185E
No target volumes were specified for the set 'volumes_set_#' in the file 'filename'.
FMM0186E
The backup ID (timestamp) is empty. This snapshot backup cannot be used for a snapshot restore.
FMM0187I
Creating a semaphore for the critical part of importing/exporting ...
FMM0188I
Trying to set the semaphore for the critical part of importing/exporting ...
FMM0189I
Semaphore released.
FMM0190W
The semaphore could not be created. System error sys_errno: sys_message
FMM0191W
The semaphore could not be initialized. System error sys_errno: sys_message
FMM0192W
The semaphore could not be allocated. System error sys_errno: sys_message
FMM0193W
The semaphore could not be released. System error sys_errno: sys_message
FMM0196I
This is your last chance to stop the Snapshot Restore. Enter 'c[ont]' to continue, 's[top]' to cancel.
FMM0199W
One or more errors were found disabling the production system resources.
FMM0200E
The following remote mirror relationships are not assigned to a consistency group: 'list of rc relations'.
FMM0201E
The NLS catalog could not be loaded. Make sure that the catalog <fully_qualified_catalog_name> exists.
FMM0202E
You cannot run the function 'function' if the restore status indicator (RSI) on target set 'id' has a value of 'RSI_START'.
FMM0203E
The following Metro or Global Mirror target volumes are in different clusters: 'listOfVdisks'.
FMM0204E
Parameter TAKEOVER_HOST_NAME is required in the storage section of the profile for a restore into the takeover host.
FMM0205I
The database is now ready for Snapshot.
FMM0206E
The source volumes are in multiple remote consistency groups.
FMM0207E
The following source volumes are either not in a remote mirror relationship or not the master volume: 'list of volumes'.
FMM0208E
The state 'cgstate' of the Metro Mirror consistency group 'cgname' is not valid for a consistent FlashCopy backup.
FMM0210W
The following Global Mirror consistency group is still copying: 'cgname'.
FMM0211I
Waiting 'resttime' seconds, but not exceeding the value TIMEOUT_FLASH of 'timeout' seconds ...
FMM0212I
New assigned Backup Sequence Number (blank)backup sequence number
FMM0213E
IBM Tivoli Storage FlashCopy(R) Manager does not overwrite the ACS_REPOSITORY repository path created with Tivoli Storage Manager for Advanced Copy Services(R) as this would invalidate all FlashCopy backups created with Tivoli Storage Manager for Advanced Copy Services(R). If you specify a different path for parameter ACS_REPOSITORY, you can continue to restore FlashCopy backups created with Tivoli Storage Manager for Advanced Copy Services(R) until the target set is reused by IBM Tivoli Storage FlashCopy(R) Manager. Optionally, you can remove the current ACS_REPOSITORY if it is acceptable to lose FlashCopy backups created with Tivoli Storage Manager for Advanced Copy Services(R). In either case, backups to Tivoli Storage Manager created by Tivoli Storage Manager for Advanced Copy Services(R) remain available for restore.
FMM0214W
The restore status indicator (RSI) has a value of 'RSI_INVALID' on target set 'id'.
FMM0215E
The state of the Global Mirror consistency group has not become the value 'consistent synchronized' inside the required periode of time.
FMM0216E
The state 'cgstate' of the Global Mirror consistency group 'cgname' is not valid for a consistent FlashCopy backup.
FMM0217E
The primary source volume with serial number 'sernumber' is attached to the local host. A remote backup can only be restored on the takeover host.
FMM0218E
The storage device has not the minimum required firmware version 'version'.'release'.'revison' installed.
FMM0219E
A timeout occurred while waiting for the 'cgname' consistency group that contains the Global Mirror relationships with Change Volumes to be synchronized on remote site.
FMM0220E
The Global Mirror 'cgname' consistency group must have change volumes assigned.
FMM0225I
Enabling the volumes and filesystems ...
FMM0226E
The following line could not be parsed:infile line
FMM0227E
The address of the datastore 'datastore URL' is not valid. It is not part of the backup.
FMM0228E
No virtual machines are available for processing after the input file is evaluated.
FMM0229E
The datastore 'datastore name' contains LUNs from more than one storage subsystem. IBM Tivoli Storage FlashCopy(R) Manager can support LUNs from only one storage subsystem.
FMM0230E
The backup type 'backup type' is not valid.
FMM0231W
The raw device-mapping disk(s) 'disk names' of the virtual machine 'VM name' are excluded from backup. A later restore of the virtual machine is possible, but the restore does not include these disks.
FMM0232I
Deleting the remote mirror relationships for the consistency group: 'cgname'.
FMM0233W
For the virtual machine 'VM name' the backup mode SNAPSHOT_INCL_MEM is changed to SNAPSHOT_EXCL_MEM because it has independent disk(s) attached: 'disk names'.
FMM0234W
The raw device-mapping disk(s) 'disk names' of the virtual machine 'VM name' were excluded during backup. Thus the restored virtual machine does not include these disks.
FMM0235I
Stopping the remote mirror relationships for the consistency group: 'cgname'.
FMM0236I
Disabling the volumes and filesystems ...
FMM0237I
Starting the remote mirror relationships for the consistency group: 'cgname'.
FMM0238W
The original resource pool path cannot be found: 'resource pool name'. The virtual machine 'VM name' is restored to the root resource pool of the host 'host name'.
FMM0239W
The raw device mapped disk(s) 'disk names' of the virtual machine 'VM name' were excluded during backup. Thus, they have been removed from the configuration of the attached virtual machine.
FMM0240E
The parameter HARDWARE_ID_LVM_MIRROR for the target set 'target_set_id' is set in the .fct-file 'file_name', but the production logical volumes are not mirrored.
FMM0261I
A disk-only backup (option -d) was invoked, forcing the parameter 'FLASHCOPY_TYPE' of the .fcs-file to 'COPY'.
FMM0265W
A new background monitor has been started. The currently registered background monitor will shut down now and the new background monitor will be used for further processing.
FMM0266E
The storage device <storage device> is not supported.
FMM0267I
Adding the remote mirror relationships to the consistency group: 'cgname'.
FMM0268E
The information of the source / target volumes could not be found.
FMM0281W
Warning: Could not connect to the admin assistant.
FMM0282E
The incremental FlashCopy cannot be refreshed. Possible reasons are:1. You added a new source volume2. You tried to start an offline FlashCopy Backup after an online FlashCopy BackupProblem solution: Run the withdraw function with option '-n TargetSetID'and afterwards restart the FlashCopy Backup.
FMM0283E
The incremental FlashCopy cannot be refreshed.The source/target pairs are not in an incremental FlashCopy relation.Problem solution: Run the withdraw function with option '-n TargetSetID'and afterwards restart the FlashCopy Backup.
FMM0285W
All source/target pairs are in an incremental FlashCopy relation.DP for Snapshot Devices will override the value 'flashcopy type' of the parameterFLASHCOPY_TYPE to 'INCR'.
FMM0286I
All source/target pairs are in an incremental FlashCopy relation.
FMM0287I
No source/target pairs are in an incremental FlashCopy relation.
FMM0288I
Not all source/target pairs are in an incremental FlashCopy relation.
FMM0309E
Cannot read file: filename.
FMM0310E
Cannot write file: filename.
FMM0311E
Request canceled by user
FMM0312E
The 'datastore name' datastore is not attached to a host.
FMM0313E
Environment variable env_var is not correct!
FMM0314E
File not found or not accessible: 'filename'.
FMM0315E
The effective user ID of the process could not be set to the user 'userid'.
FMM0318W
Warningcolon; File 'file name' still exists on the backup system.
FMM0320W
The free space in the file system containing the directory path is only amountMB.
FMM0321E
IBM Tivoli Storage FlashCopy(R) Manager requires a free space of at least 5 MB in the file system containing the directory path.
FMM0322E
The environment variable env var could not be set!
FMM0323E
File 'file' was not found on the target disks.
FMM0324W
Environment variable env var has value 'value'.
FMM0325E
Environment variable env var could not be unset! Unset this variable and restart.
FMM0326I
Environment variable env var is successfully unset.
FMM0327E
Operating system error error_no: message text
FMM0328E
IBM Tivoli Storage FlashCopy(R) Manager requires at least amount_required of free space in the file system containing path. Available free space: amount_available.
FMM0329E
The LUN 'LUN name' is needed for this operation but cannot be accessed.
FMM0330E
The datastore with the name 'datastorename' was not found. It is not part of the backup.
FMM0331I
The file 'filename' is locked, waiting one second and retry!
FMM0332I
Suspend the database activity.
FMM0340I
Complementary LVM/ASM mirror items that are not needed for the snapshot: backup_items were found.
FMM0341W
The status information for the fsname file system cannot be read. The following error message was generated by the operating system: txtmsg.
FMM0347E
The update of the IDS repository failed.
FMM0348E
The following auxiliary vdisk: 'aux vdisk' is mapped to host 'host name'. It should be mapped to takeover host 'takeover host' only.
FMM0349E
The target set 'targetSetID' does not match the source volumes.
FMM0350E
A background copy process of type 'CopyType' is still running on target set 'targetSetID'.
FMM0351I
The target set with ID 'targetSetID' is selected for this run.
FMM0352E
No target set found to accept a backup of type 'copy_type'.
FMM0353E
Background copy process on the oldest target set 'target set' still running.
FMM0354E
The copy type argument 'copy_type' is not valid.
FMM0355E
Unable to connect to the copy services server 'csname'.
FMM0356E
You cannot run a Snapshot restore from target set 'targetSetID from' if the sources are involved in a relationship of type 'copytype' with the target set 'targetSetID'.
FMM0357I
FlashCopy type is 'copy_type'.
FMM0358E
An invalid value 'copy_type' has been specified for the FlashCopy type in the profile '.fcs file'.
FMM0361E
The target set must be specified over the option -n, if the parameter EXTERNAL_LVM_PLUGIN is set.
FMM0364E
Parameter 'parameter ' is mandatory.
FMM0365E
The data center with the name 'dcname' was not found.
FMM0366E
The following line in the domain input file could not be parsed: 'inputline'.
FMM0367I
The scope is being limited to the following data center(s): 'dcnames'.
FMM0368I
Stopping the consistency group 'cgname' and all its older dependents.
FMM0369W
The data center that is named 'dcname' is part of the current domain configuration but was not found in the vCenter(TM).
FMM0370W
The parameter 'profile_value' is deprecated.
FMM0378E
The value of the parameter 'parameter_name' in the device section of the profile is invalid.
FMM0389E
Errors occurred during the deletion of one (or more) backups.
FMM0390E
The virtual machines with the specified instance UUIDs have not been found in the backup. Update the input file with valid instance UUIDs. Listing missing UUIDs:instance uuids
FMM0391E
The 'datastore name' datastore could not be attached to the 'hostname' host. Please look up the message user response in the users guide for a step-by-step guide how to solve this problem.
FMM0392E
The 'datastore name' datastore could not be attached.
FMM0393E
The target instance UUID 'target instance uuid' specified in the input file cannot be found. Add a valid target instance UUID to the input file.
FMM0394E
Redirected restores are not allowed for distributed virtual machines. The virtual machine 'VM name' spans multiple datastores and is distributed. Do not specify a target VM name or a target datastore for the restore operation.
FMM0395E
This license does not allow to use LVM mirrors.
FMM0396E
DB2 for Advanced Copy Services does not support file systems that cannot enable freeze or thaw operations.
FMM0397E
You cannot freeze filesystems of type JFS.
FMM0398E
Consistency group cgname is not valid (state: status) to perform a FlashCopy restore.
FMM0399W
Timestamp ->timestamp<- cannot be converted.
FMM0400I
The process is waiting for BRBACKUP.
FMM0401I
The 'original VM name' virtual machine has been registered with the new name, 'new name'.
FMM0402I
The 'datastore name' datastore with the new datastore name 'new datastore name' was successfully attached to the 'ESX host name' ESX host.
FMM0403I
All the virtual disks (exclusive of RDM disks) on the virtual machine 'source vm name' are attached to the target virtual machine 'target vm name'.
FMM0404I
The virtual disks on the virtual machine 'source virtual machine name' with the disk keys 'diskkeys' are attached to the target virtual machine 'target virtual machine name'.
FMM0405I
The process waited num_sec seconds for BRBACKUP in util_file_online communication.
FMM0406W
The 'vm name' virtual machine is a distributed VM because the 'virtual disk name' disk is located in the 'disk directory' datastore directory, which is not the 'working directory' VM working directory.
FMM0407E
The maximum number of SCSI targets for a virtual machine is exceeded.
FMM0408E
The disks with the 'diskkeys' disk keys cannot be found in the backup and are not attached.
FMM0409E
There is not enough free space available in the 'datastore name' target datastore to complete this operation. space needed is required to complete this operation. space available is free.
FMM0410E
Cannot open or delete switch file 'file name'. Check permissions.
FMM0411E
Maximum time waiting for BRBACKUP expired.
FMM0412E
BRBACKUP wasn"t able to switch requested tablespace in BEGIN/END BACKUP mode.
FMM0413E
Error while requesting tablespace switch.
FMM0414E
Error while requesting tablespace switch.
FMM0415E
The 'datastore name' datastore cannot be found. In the input file the named datastore is specified as a target datastore for the restore operation.
FMM0416E
The 'vm name' virtual machine could not be restored to the 'target datastore' datastore using 'target vm name' VM name. A VM with the same name already exists in the datastore.
FMM0417I
The 'source vm name' virtual machine is successfully restored to the 'datastore names' datastore(s) and registered with the name 'registered vm name'.
FMM0418I
The attached virtual disk with the 'disk key' key is successfully detached from the 'virtual machine name' virtual machine.
FMM0419E
The configured vCenter server supports the 'found API version' API version. The requested operation is available since the 'needed API version' API version and is not supported by the configured vCenter server.
FMM0420E
The 'ESX hostname' ESX host supports the 'found API version' API version. The requested operation is available since the 'needed API version' API version and is not supported by the ESX host.
FMM0421E
The restore operation cannot be completed because the 'vm name' virtual machine with 'vm instance uuid' instance UUID is not powered off.
FMM0422E
A virtual disk was not found for the 'diskkey' disk key as specified in the input file.
FMM0423I
The 'diskname' virtual disk on the 'virtual machine name' virtual machine was successfully restored.
FMM0424I
Start Snapshot backup destinationbackup typesid host productive host backuphost listsid list
FMM0425I
flashcopy type Start Snapshot background copy
FMM0426I
The following virtual machine question has been answered to with 'answer':question
FMM0427I
Stop Snapshot background copy
FMM0428I
Start Withdraw
FMM0429I
Stop Withdraw
FMM0430I
Enabling the volumes and filesystems finished
FMM0431E
One or more vmware snapshot operations failed.
FMM0432E
The vmware snapshot operation for the virtual machine with instance uuid 'instance uuid' failed: 'error'.
FMM0433W
The vmware power on operation for the virtual machine 'vmref' failed: 'error'.
FMM0434W
The remove operation of the vmware snapshot 'snapref' failed: 'error'.
FMM0435E
The virtual machine 'VM name' can not be restored because the backup is in use by an offloaded TSM backup. The restore of a distributed VM is not allowed if an offload TSM backup is in progress. Wait until the offload backup is complete.
FMM0436E
The virtual machine 'VM name' could not be restored because the backup is already in use by an other VM.The restore of a distributed VM is not allowed if the mounted datastore is already in use by a VM.Detach this backup. Try the operation again.
FMM0437E
The virtual disks cannot be added or replaced on the 'vm name' virtual machine with 'vm instance uuid' instance UUID identifier. The specified virtual machine is suspended.
FMM0438E
The virtual disks cannot be removed from the 'vm name' virtual machine with 'vm instance uuid' instance UUID identifier. The specified virtual machine is suspended.
FMM0439W
The vmware snapshot operation for the virtual machine with instance uuid 'instance uuid' failed: 'error'. The backup of this virtual machine will be crash consistent only.
FMM0440I
The following virtual machine question has been answered to with 'answer':question
FMM0441W
The VMware snapshot operation for the virtual machine with 'instance uuid' instance UUID cannot be completed: 'error'. Trying the VMware snapshot again without quiescing the file system.
FMM0451E
The disk with the 'diskkeys' disk key is a raw device-mapping disk which must not be attached.
FMM0452E
This version of Data Protection for SAP(R) has expired.
FMM0453W
This version of Data Protection for SAP(R) will expire in number days.
FMM0454I
*** This copy is NOT FOR RESALE. ***
FMM0455E
License file file name does not exist.
FMM0456E
Unable to access license file file name.
FMM0457E
License file file name contains invalid data/checksum.
FMM0458I
Fake-Mode is activated.
FMM0459E
One or more suspend operations failed.
FMM0460E
No mux file is found with the name name
FMM0461I
Created tracefile 'tracefile' for process ID 'id'.
FMM0503E
Unexpected error occurred.
FMM0504I
A software snapshot including memory is created of the 'vm name' virtual machine with the 'vm instance uuid' instance UUID.
FMM0505I
A software snapshot excluding memory is created of the 'vm name' virtual machine with the 'vm instance uuid' instance UUID.
FMM0506I
The 'vm name' virtual machine with the 'vm instance uuid' instance UUID is suspended.
FMM0507I
The software snapshot of the 'vm name' virtual machine with the 'vm instance uuid' instance UUID is removed.
FMM0508E
The 'vm name' virtual machine might be the virtual machine containing IBM Tivoli Storage FlashCopy(R) Manager and cannot be part of the backup. Rename it or specify the virtual machine containing IBM Tivoli Storage FlashCopy(R) Manager in the 'profile parameter name' profile parameter in the profile.
FMM0509E
More than one instance of this executable are running now.
FMM0510E
acsgen has to be started from the CLI with the required '-D' parameter.
FMM0511I
====>Performing IBM Tivoli Storage FlashCopy(R) Manager v1 command.
FMM0512E
The virtual machine containing the vCenter server cannot be part of the backup. The 'vm name' virtual machine is part of the backup but it is specified as the vCenter server virtual machine in the 'profile parameter name' parameter in the profile.
FMM0513E
The 'vm name' virtual machine might be the virtual machine containing the vCenter server and cannot be part of the backup. Rename it or specify the virtual machine containing the vCenter server in the 'profile parameter name' profile parameter in the profile.
FMM0514E
The virtual machine that contains IBM Tivoli Storage FlashCopy(R) Manager cannot be part of the backup. The 'vm name' virtual machine is part of the backup but it is specified as the virtual machine containing IBM Tivoli Storage FlashCopy(R) Manager in the 'profile parameter name' parameter in the profile.
FMM0515E
Filesystem consistency check failed.
FMM0516E
The initialization of the ODM API failed with ODM error number odmerrno: description.
FMM0517E
Failed to get the ID of the volume group vgname using the AIX command: command.
FMM0518E
Failed to get the ID of the logical volume lvname using the AIX command: command.
FMM0519E
The volume with the serial ID serialid is not assigned to the backup host.
FMM0520W
Trying to find the process that has locked the ODM ...
FMM0521I
Waiting the maximum seconds seconds until the ODM lock is released by another application.
FMM0522E
The storage system ID could not be found for the volume volume.
FMM0523E
The file systems needed for the mount operation are missing.
FMM0524E
The pathname directory path or fully qualified file name was not found in any of the current active file systems.
FMM0525E
Mount point mount_point_name is not recognized by the system.
FMM0539E
Either Oracle control file or redo log file is in the same volume group (v1) with which Oracle datafiles are.
FMM0540E
A null logical volume has been detected.
FMM0542I
Mounting disk group : dg1.
FMM0543I
Mounting filesystem : fs1.
FMM0544E
Serial number for the device v1 is not found.
FMM0545I
Trying to find new devices to match the source device. This process will take some time.......
FMM0546I
Removing device : parm1
FMM0547I
Configuring the target volume would cause duplicate physical volume ID : pvid1.
FMM0548E
Removing device parm1 failed.
FMM0549W
Removing the mount point directory mntpt1 failed with rc: rc1.
FMM0550E
The physical volume ID pvid1 is duplicate on the production machine.
FMM0551W
The umount command failed with rc rc1 for mount point mntpt1.
FMM0552E
A backup with the 'backup_id' ID cannot be found.
FMM0553E
Failed to suspend I/O on a logical volume device with errno errno for logical volume: lv.
FMM0554E
Failed to resume I/O on a logical volume device with errno errno for logical volume: lv.
FMM0555E
Multiple backup IDs were specified in the input file. You can specify only one backup ID in the input file.
FMM0556I
Flashcopy type is set to NOCOPY. Removing disk meta data for all target disks... This backup is NOT valid for a FlashCopy restore. Please restore from TSM Server.
FMM0557W
Removing the file system on the mount point mntpt1 failed with rc: rc1.
FMM0558I
Flashcopy type is set to COPY or INCR. Leaving disk meta data intact for all target disks... This backup is valid for a FlashCopy restore.
FMM0559E
Command lslv failed for the logical volume v1.
FMM0560E
Unsupported file system has been detected.
FMM0561E
The file or directory objname must not be located on the volume group v1.
FMM0562E
No backup ID was found in the input file. Specify a valid backup ID in the input file.
FMM0563E
An physical disk for the volume group v1 was not found.
FMM0564I
Exporting volume group fnm1 failed.
FMM0565I
Importing volume groups now...
FMM0566I
Newly imported volume group: vg1
FMM0567E
Logical Volume cannot be found for the file fnm1.
FMM0568I
Removing volume group fnm1 ....
FMM0569I
Varied off and exported volume group : fnm1
FMM0570I
Finding the serial numbers ...
FMM0571E
The vmcli executable file 'vmclipath' does not exist. The installation seems to be corrupt.
FMM0572E
No volume group was found.
FMM0573E
Volume group vg1 can not be found.
FMM0574E
Quorum of the volume group vg1 must be off.
FMM0575E
Logical volume vg1 must have at least 2 copies.
FMM0576E
Logical volume vg1 must have the parallel or striped scheduling policy.
FMM0577E
Logical volume vg1 must have mirror write consistency on.
FMM0578E
None of the mirror copies of the logical volume lv resides completely on the specified hardware unit essid.
FMM0579E
Some of the partitions of vg1 are stale on the specified hardware unit identifier.
FMM0580I
Could not determine the number of paths to target volumes. Using default value of 1.
FMM0581E
Failure in changing the mount point mp, return code rc from command chfs.
FMM0582E
The same hdisk vg1 can not be associated with two different vpaths (serial numbers vg2 and vg3). command chfs.
FMM0583E
lsvg command failed.
FMM0584I
Recreating the new volume groups....
FMM0585E
The command lvm_queryvg failed.
FMM0586E
The number of new volume groups is limited parm1.
FMM0587I
Varying on volume group fnm1 failed.
FMM0588E
Invalid option found in the Setup File.
FMM0589I
Flushing the buffers to disk...
FMM0590I
Unmounting the file system mntpt1...
FMM0591I
Bringing up the volume groups...
FMM0592I
Too many file systems located.
FMM0598E
Although the pvid pvid is contained in the descriptor area of the volume group vgname, no logical devices (hdisk/vpath) has this on the production system.
FMM0599E
Physical volume hdisk is in the descriptor area of the volume group vgname but does not belong to this volume group.
FMM0600W
The major number of the volume group vgname could not be determined.
FMM0601W
Major number major already exists on the production machine. The system will assign the next available major number to the volume group vgname.
FMM0602E
Production database does not reside on a LVM mirror environment. The profile parameter 'profile_param' is not allowed in an environment without LVM mirroring.
FMM0603E
Error reading the status information of the file system fsname: txtmsg.
FMM0604W
The file system fsname is not of type jfs2. The freeze/thaw function will be applied only on file systems of type jfs2.
FMM0605E
Error freezing the file system fsname: txtmsg.
FMM0606E
Error thawing the file system fsname: txtmsg.
FMM0607I
Freezing filesystem : fs1.
FMM0608I
Thawing filesystem : fs1.
FMM0609I
Performing snaprestore of the source volume srcvol to the snapshot snapid (LUN lunpath).
FMM0610I
Performing snapshot of the source volume srcvol (LUN lunpath).
FMM0611I
The snapshot snapid was generated for the source volume srcvol (LUN lunpath).
FMM0612E
File system fsname thawed automatically because the specified timeout limit was exceeded. Specify the profile parameter TIMEOUT_FLASH, to increase the timeout limit. The default value of this parameter is 120 seconds.
FMM0613E
File system fsname can not be freezed because the timeout limit was exceeded. Specify the profile parameter TIMEOUT_FLASH, to increase the timeout limit. The default value of this parameter is 120 seconds.
FMM0614E
The process failed to update the usability state of the snapshot backup.
FMM0615E
Unable to open file file1.
FMM0616I
Performing fctype FlashCopy of source volume src1 to target volume tgt1
FMM0617W
The locale 'locale' for the host is not supported by the vCenter(TM) server. A default locale will be used.
FMM0618E
The suspend operation for the virtual machine with the instance UUID 'instance uuid' failed: 'error'.
FMM0619I
Performing FlashCopy withdraw of source volume src1 from target volume tgt1
FMM0620E
No target volume is available. Terminating......
FMM0635E
A required parameter tgtv1 is missing in the Setup File.
FMM0643I
Executing system command 'parm1'
FMM0644E
Error on running command: parm1
FMM0647I
User abort; Exiting Flashcopy Restore.
FMM0648I
User input was yes; Continuing Flashcopy Restore.
FMM0649I
You are about to perform a Flashcopy Restore operation. All data on the source volumes, including (but not limited to) filesystems and raw volumes, will be lost. Do you want to continue? Please enter Yes or No.
FMM0650I
A Flashcopy Restore operation has been requested, with Prompt=No. All data on source volumes, including (but not limited to) filesystems and raw volumes, will be lost. Continuing Flashcopy Restore operation.
FMM0651E
The 'prefix' prefix is not contained in the string 'searchstring' in the input file.
FMM0652E
Invalid license is detected.
FMM0653I
The 'operation' request processed successfully.
FMM0654E
The following instance UUIDs have not been found in the datastores that are included in the backup. They are not part of the backup.instance uuids
FMM0655E
The 'prefix' prefix in the input file is not allowed for single disk restore operations.
FMM0656E
An error has been detected when running the TSM Backup Archive Client command line interface.
FMM0657E
A memory allocation error has occurred.
FMM0665E
There are multiple NFS servers involved: the NFS server 'nfsserver1' for the file 'filename' is different from the previous NFS server 'nfsserver2'.
FMM0666E
Could not open trace file v1.
FMM0667E
Could not create the trace object.
FMM0668E
Invalid trace flag: v1.
FMM0672E
Error while querying volume properties of volume volserial. Please verify that the volume specified in the target volumes file exists.
FMM0673E
A Flashcopy background copy is in progress between source volume: source volume and target volume: target volume.
FMM0674E
A Flashcopy association exists between source volume: source volume and a different target volume: target volume.
FMM0675E
An unexpected error was encountered. function name : function-name function : function-desc return code : rc file : file-name (line-number)
FMM0676E
program-name: cannot open file file-spec: error.
FMM0710E
Unable to close trace output file file-name.
FMM0711E
Unable to write to trace file tracefile. Tracing disable d.
FMM0712E
Invalid trace file name (name too long).
FMM0727E
Specifying the trace file 'link' as a symbolic link is not allowed.
FMM0728E
Symbolic link 'linkname' to 'target' was successfully deleted.
FMM0729E
Unable to delete symbolic link 'link'.
FMM0739E
Invalid trace keyword - 'keyword'
FMM0740E
Unable to open trace output file file-name.
FMM0741E
The physical volumes of the volume group v1 were not found.
FMM0742E
Varying off volume group fnm1 failed.
FMM0743I
<fn1> (blank)VOLUME GROUP : fn2 (blank)COPIES : fn3 (blank)SCHED POLICY : fn4 (blank)STALE PPs : fn5 (blank)MIRROR WRITE CONSISTENCY: fn6
FMM0744I
<lvname><copy><pv><serialno><status>
FMM0745W
Logical volume vg1 has vg2 stale partitions.
FMM0746E
The source volume with serial number cmd is not attached to the production system.
FMM0747E
The source volume with serial number cmd belongs to another volume group.
FMM0748W
The logical volume lv on the mount point mp was renamed or newly added.
FMM0749I
List of the current file systems on the backed up volume groups ...
FMM0750I
List of file systems which will be restored...
FMM0753W
The newly added volume cmd will be deleted from the database volume group rc.
FMM0754I
Logical volume lv was removed during Flashcopy Restore, because it was newly added since last backup, needs to be recreated manually.
FMM0755I
The following commands should be run after the FlashCopy process in background is finished to synchronize the LVM copies:
FMM0756E
Error converting the hdisk device volume group vg to a Subsystem Device Driver vpath device volume group.
FMM0757W
The rmlv command lv ended with return code rc.
FMM0758E
DP for Snapshot Devices encountered a problem when using the FlashCopy function of the Copy Services.
FMM0759E
The file system fs already has an entry in the /etc/filesystems.
FMM0760W
The reducevg command cmd ended with return code rc.
FMM0761W
The extendvg command cmd ended with return code rc.
FMM0762W
The mklvcopy command cmd ended with return code rc.
FMM0763I
Removing copies from the logical volumes ...
FMM0764I
Removing physical volumes from the volume groups ...
FMM0765I
Adding physical volumes to the volume groups ...
FMM0766I
Adding copies to the logical volumes ...
FMM0767W
The command cmd ended with return code rc.
FMM0768E
Importing the volume group from hdisk logdev failed.
FMM0769E
Recreating the volume group from the hdisks hdisks failed.
FMM0770I
Removing the logical device logdev with the same PVID pvid in the ODM.
FMM0771I
Could not mount all the filesystems originally present.
FMM0772W
The database volume groups do not contain currently any file system.
FMM0773W
One or more errors were found disabling the production system resources. However, the FlashBack restore will continue.
FMM0774I
The 'diskname' virtual disk on the 'virtual machine name' virtual machine is successfully restored to the 'target virtual machine' virtual machine and is added to its configuration.
FMM0775E
The label of the logical volume lvname is missing. Set it using chlv -L mountPoint logicalVolume.
FMM0776I
Number of volumes to be processed by Flashcopy: v1
FMM0777E
An unexpected error was encountered processing a function. function name : function-name function : function-desc return code : rc file : file-name (line-number)
FMM0778E
SVC virtual disk v1 is not valid. Please verify that the volume specified in the target volumes file exists.
FMM0779E
The source v1 and target v2 virtual disks are in different SVC clusters.
FMM0780E
The source v1 and target v2 virtual disks are of different size.
FMM0781E
An error was returned calling an operation of the Common Interface Model(CIM). function name : function-name received msg : function-desc CIM return code: 0xCIM-rc file : file-name (line-number) If the received message contains 'CIM Error', then please collect the CIM Agent logs and send them to CIM support.
FMM0782E
A memory allocation error has occurred in file filename, line number linenumber.
FMM0783E
The execution of command 'lscfg' failed. Please verify that the command 'tset -I -Q' is not set in the users environment files .profile, .login .dbenv_<hostname>.sh, .dbenv_<hostname>.csh and .sapenv_<hostname>.sh, .sapenv_<hostname>.csh.
FMM0784I
The ONTAP filer version on this appliance is: n.
FMM0785W
The option fractional reserve on volume vol_name was reduced to less than 100 percent.
FMM0786I
Removing the snapshot snapshot name of source volume source volume (LUN LUN path)
FMM0787E
The snap restore for volume volname with snapshot name snapname would destroy later snapshots that are required for other applications or for volume clones.
FMM0788W
IBM Tivoli Storage FlashCopy(R) Manager did not find any snapshots for volume volname on the N series filer.
FMM0789W
IBM Tivoli Storage FlashCopy(R) Manager did not find any information about the N series volume volname.
FMM0790E
The snapshot name snapname for volume volname was not found in the snapshot list on the N series filer.
FMM0791W
Function refreh incremental FlashCopy cannot be accomplish because no consistency group found for these volumes.
FMM0792E
The list of volumes passed contain pairs which belong to different consistency groups in the scope of one single cluster.
FMM0793W
No FlashCopy relationships found in the storage system.
FMM0794E
The state status of the consistency group is bad to achive a valid disk backup.
FMM0795E
Error initializing the connection to the copy services server.
FMM0796I
Trying to connect to primary copy services server 'cs_primary'.
FMM0797I
Trying to connect to primary 'cs_prim' and/or secondary 'cs_sec' copy services server.
FMM0798I
The primary copy services server 'cs_prim' is not responding. The following CIM error was reported: cim_err_msg Working with secondary copy services server 'cs_sec'.
FMM0799E
The primary copy services server 'cs_prim' is not responding. The following CIM error was reported: cim_err_msg
FMM0800E
Neither the primary 'cs_prim' nor the secondary copy services server 'cs_sec' are responding. The following CIM error was reported: cim_err_msg
FMM0801W
The FlashCopy direction in the consistency group cs_name is switched. A withdraw will be done prior to continue.
FMM0808E
Operating system command 'command' failed; rc=rc.
FMM0809E
The primary and secondary copy service servers are down.
FMM0810E
Cannot open the command output file v1 for writing.
FMM0811E
The LUN are already in use.
FMM0812I
The backup DB2 UDB preview command indicates there are sufficient resources for a backup operation.
FMM0836E
Error while invoking the diskmapper.
FMM0837E
The path 'v1' is not a character device.
FMM0838W
The following files have been found in the diskgroup allthough they do not belong to the database and are not contained in the negative list: 'files'.
FMM0839E
Not all disks of the failure group 'failureG' of diskgroup 'diskG' were found on the configured storage subsystem. This failure group is excluded from further processing.
FMM0840E
Not enough failure groups for redundancy type 'redType' in diskgroup 'diskGroup'. 'foundFG' have been found but 'neededFG' are needed for this redundancy type. Please make sure that the currently selected DEVICE_CLASS contains enough failure groups for a consistent flashcopy and ensure that they are online.
FMM0841E
Not all disks reside on the same cluster. Disks were found on the cluster with id: 'first cluster id' and on the cluster with id 'second cluster id'.
FMM0842E
The ASM diskgroup 'diskGroup' could not be dropped but is still available in the ASM instance. Restore will be stopped.
FMM0843E
The ASM diskgroup 'diskGroup' could not be unmounted and is still mounted in the ASM instance. Unmount will be stopped.
FMM0844E
No target volume is available for serial 'serial'.
FMM0845E
The volume manager of your profile is not set to ASM, the found value is 'serial'. Ensure that you have set the right volume manager in your profile.
FMM0846E
You have SDD installed on your system, but SDD is currently not supported by this product when using Oracle ASM.
FMM0847E
Error occured while checking the 'db2nodes.cfg' on the production system and on the clone system. The 'db2nodes.cfg' on the production system contains production system entries entries, whereas the 'db2nodes.cfg' on the clone system contains clone system entries entries.
FMM0848E
Error occured while checking the 'db2nodes.cfg' on the production system and on the clone system. The database partition partition number configured on the production system is not configured on the clone system.
FMM0849E
Error occured while checking the 'db2nodes.cfg' on the production system and on the clone system. The hostname 'host name' where partition partition number resides is contained in the 'db2nodes.cfg' on the production system as well as on the clone system. Either the setup of the 'db2nodes.cfg' file on the clone system is wrong or the clone system was configured on the same host as the production system.
FMM0850I
To synchronize the volume groups that have stale partitions you can use the following commands:
FMM0851E
The copyservices timeout value of fsname minutes was reaced while waiting for an answer of the copyservices CIM agent. Specify increase the value of the profile parameter COPYSERVICES_TIMEOUT in the DEVICE_CLASS section of the profile, to increase the timeout limit. The default value of this parameter is 6 minutes.
FMM0852E
It is not allowed to establish a second incremental FlashCopy relation from a source volume source volume to a target volume target volume while another incremetal FlashCopy relation from the same source volume to a different target volume already exists.
FMM0853E
During the mount operation IBM Tivoli Storage FlashCopy(R) Manager identified that the following source volumes are visible on the backup or cloning system 'host name'. This can be caused by misconfiguration in the storage system or by misconfiguring the IBM Tivoli Storage FlashCopy(R) Manager backup or cloning system to the same host as the production system. List of visible source volumes: source volumes
FMM0854E
During the mount operation IBM Tivoli Storage FlashCopy(R) Manager identified that the following target volumes are not visible on the backup or cloning system 'host name'. List of missing target volumes: target volumes
FMM0855E
During the mount operation IBM Tivoli Storage FlashCopy(R) Manager identified that the following target volumes are not visible on the ESX host 'host name'. List of missing target volumes: target volumes Either the volumes could not be assigned to the host correctly or you used PRE_ASSIGNED_VOLUMES for the TARGET_SETS parameter in your Device Class section and the target volumes are not assigned to this ESX host.
FMM0856E
The datastore 'datastore name' cannot be attached to the ESX host: 'host name', the datastore is already attached to another ESX host. You must detach the data store that is currently attached to the ESX host and try the task again.
FMM0857E
The virtual disks of the source virtual machine 'source vm name' cannot be attached because a disk is already attached to a target virtual machine. Detach all virtual disks of the source virtual machine and try the attach task again.
FMM0858I
The Oracle recovery catalog check (fcm.catalog_db_connection) validates if the database is registered in the Oracle RMAN recovery catalog.
FMM0859E
An error occurred in the connection to the Oracle recovery catalog: rman output shell group
FMM0860E
The Oracle database is not registered in the Oracle recovery catalog.
FMM0861E
The command line option -r is missing.
FMM0862E
The value AUTO is not supported for ASM_INSTANCE_USER parameter.
FMM0863I
IBM Tivoli Storage FlashCopy(R) Manager detected the ACFS device: 'vol_dev', with mount point: 'mnt_pt', in disk group: 'dg_name'.
FMM0864W
IBM Tivoli Storage FlashCopy(R) Manager detected the ACFS device: 'vol_dev', with mount point: 'mnt_pt', in disk group: 'dg_name'.
FMM1000E
syntax error in line line : 'statement'
FMM1001E
syntax error in file 'file name'. Exiting program.
FMM1002E
BACKUPIDPREFIX must be number_of_characters characters!
FMM1003W
Please set redolog_copies to a number between min_copies and max_copies a.(blank) Now it is set to act_copies.
FMM1004W
ou should specify the BACKUPIDPREFIX before the TRACEFILE statement.(blank) So that the BACKUPIDPREFIX can be used in the tracefilename.
FMM1006E
The SERVERNAME must be less than max_char characters.
FMM1007E
The NODENAME must be less than max_char characters.
FMM1008E
The MANAGEMENTCLASSNAME must be less than max_char characters.
FMM1009W
Please set MULTIPLEX to a number between 1 and max_multiplex.(blank) Now it is set to act_multiplex.
FMM1011W
The sortfilename 'sortfile_filename' should be absolute!
FMM1012E
Configfile not found or permission denied: 'configuration_filename'.
FMM1013E
Profile not found or permission denied: 'profile_filename'.
FMM1014I
Operation function was completed successfully.
FMM1015E
Operation function completed with error.
FMM1016W
The tracefilename 'file name' could not be opened for writing!
FMM1017E
The server server is already defined. Please use another name or specify TCP_ADDRESS!
FMM1019E
Failed to respond to a message received from XINT.
FMM1021E
component_name terminates the connection due to a previous error.
FMM1022E
component_name terminates the connection due to a previous error.
FMM1023W
>Could not establish connection to log server log server name.
FMM1024E
The file filename occurs twice in the <infile>
FMM1025E
You must use consistency groups when using ASM. Set the profile parameter 'profile param' accordingly.
FMM1026E
Writable snapshots must be used when running in an LVM mirroring environment. Update the profile parameter 'profile param' accordingly.
FMM1027E
The mount operation failed. Although an unmount operation can clean up the backup system, in some cases this is not possible and the cleanup must be performed manually. In this case, the unmount operation should be started after cleanup in order to start another mount operation.
FMM1029W
Device 'device' could not be opened. Received error message from the operating system: 'error_message'. This device might cause the current FlashCopy Manager operation to fail.
FMM1030E
The operating system refused a request for memory allocation.
FMM1031I
The tape backup received this ID: 'tape_backup_id'.
FMM1032E
The nodes of PARTITION_GROUP 'partition_group_name' are associated with multiple device classes: 'first_device_class', 'second_device_class'
FMM1033W
The backup 'backup_id' is not expired because it is still valid in the repository. You can either manually delete this backup or set the parameter MAX_VERSIONS to ADAPTIVE. Note that this parameter setting turns off snapshot expiration.
FMM1039E
Aborting backup. Another backup with ID 'backup_id' is already mounted on backup server: 'host'.
FMM1040E
An exception occured in the operating system adapter component, exception text: extext.
FMM1041E
Failed to identify the default DB2 instance of user DB2 instance owner. Please set the DB2 environment variable DB2INSTANCE correctly.
FMM1042E
The entry in the FLASH_DIR_LIST file is not a valid file or directory: entry.
FMM1043E
The environment is set up for the wrong database instance: 'wrong instance'. Expected instance 'expected instance'.
FMM1044E
The section CLONING is missing from the profile.
FMM1045E
The parameter TARGET_SETS VOLUMES_DIR must not be used for cloning operations.
FMM1046E
FlashCopy Cloning is not supported with FLASHCOPY_TYPE NOCOPY. Please specify COPY or INCR instead.
FMM1047E
Expected keyword 'expected keyword' but found 'wrong keyword'.
FMM1048E
Device section 'device section' can not be used for cloning. Either add 'USE_FOR_CLONING <SID>' to reserve this device class for cloning operations or choose another device class.
FMM1049E
No DEVICE_CLASS found that can be used for the current FlashCopy Cloning operation with the clone database name specified with the command line option -C <Clone DBname>.
FMM1050E
The mandatory argument argument as part of the device class parameter device class does not exist.
FMM1051E
The keyword 'use_for_cloning_keyword' is needed for the keyword TARGET_NAMING in the device class 'device class' because this device class is used for cloning.
FMM1052E
The parameter TARGET_NAMING of the device class 'device class' is not configured for cloning of the database instance 'instance'.
FMM1053E
Failed to identify the default DB2 instance of user 'user name'. The environment variable DB2INSTANCE is missing.
FMM1054E
Failed to attach to the DB2 instance 'instance'.
FMM1055E
Failed to get the DB2 database manager configuration.
FMM1056E
Failed to detach from the DB2 instance 'instance'.
FMM1057E
Failed to query the DB2 client settings.
FMM1058E
Failed to set the DB2 client parameters.
FMM1059E
Recovery of the DB2 database 'database alias' failed.
FMM1060E
Failed to set the DB2 database configuration for database 'database alias'.
FMM1061E
Failed to get the DB2 database configuration for database 'database alias'.
FMM1062E
Failed to mount the database on host 'hostname'. This is the output of the failed command:output
FMM1063E
Failed to identify the log path for partition partition number.
FMM1064E
Failed to identify the current working directory.
FMM1065E
Failed to change working directory to 'directory'Error: error number: error text.
FMM1066E
Failed to create symbolic link from 'directory/new instance' to 'instance'Error: error number: error text.
FMM1067E
Entry in the storage path file 'file' is not a valid file or directory: 'directory'.
FMM1068E
The clone instance on the clone system is running.
FMM1069E
The clone instance on the clone system is not running.
FMM1070E
Due to a mount agent is already registered on backup system 'backup system' additional mount agents have to have registered using different device classes.
FMM1071E
A mount agent is already registered on backup system 'backup system' using the device class 'device class'. Additional mount agents have to have registered using different device classes.
FMM1072E
Due to another mount agent is already registered on backup system 'backup system' using device class 'device class' and node(s) 'list of nodes' additional mount agents on host 'backup system' have to have registered using different nodes instead of 'list of nodes'.
FMM1073E
The clone database name database name commandline specified with the command line option -C does not match with the database names database name cloningsection specified in the DEVICE_CLASS parameter of the CLONING section.
FMM1074E
A FlashCopy clone was requested for clone database database name and device class device class but the parameter CLONE_DATABASE YES is not specified in this device class section.
FMM1075E
A FlashCopy backup was requested for device class device class but the parameter CLONE_DATABASE YES is specified in this device class.
FMM1076E
The target set 'target set' is used for a backup with ID 'backup ID'. It cannot be used as target set for cloning.
FMM1077E
The target set 'target set' is used for a clone with ID 'backup ID'. It cannot be used as target set for backup.
FMM1078E
The operation name cannot be started due to the FlashCopy clone(s) 'target set' is/are still copying data in the storage system from source to target.
FMM1079E
The data container 'container ID' is already subject of the operation.
FMM1080E
The database to be cloned has to have specified, because multiple databases have been found within this instance.
FMM1081E
Unable to detect the database environment.
FMM1082E
Checking the clone system status of the database 'database name' failed.
FMM1083E
Flashcopy of the database failed with rc return code.
FMM1084E
Database profile 'profile name' not found.
FMM1085E
No database control file found.
FMM1086E
Failed to start the database in nomount mode. This is the output of the failed command:
FMM1087E
Failed to rename the database. This is the output of the failed command:'command output'
FMM1088E
For cloning functions the name of the clone database must be specified.
FMM1089E
For cloning functions the name of the clone instance owner must be specified.
FMM1090E
For the pre-processing function the pre-processing configuration file must be specified.
FMM1091E
For the post-processing function the post-processing configuration file must be specified.
FMM1092E
Script terminated with errors. Return code is: return code
FMM1093E
Script 'script name' could not assigned to either shell scripts or SQL scripts.
FMM1094E
Script file 'script name' not found.
FMM1095E
The physical location of the pre-processing or post-processing configuration file and the script 'script name' is different.
FMM1096E
The script 'script name' is a symbolic link.
FMM1097E
The user 'user name' is not owner of the script 'script name'.
FMM1098E
The user 'user name' configured for script 'script name' is actually not applied on the system.
FMM1099E
The pre-processing or post-processing configuration file 'file name' is not found.
FMM1122E
The pre-processing or post-processing configuration file 'file name' does not contain any data record.
FMM1123E
Failed to open the database: output
FMM1154E
The only valid profile values for the keyword 'keyword' are 'val1' and 'val2'.
FMM1158T
Service service not completed
FMM1161E
Failed to recover the database. This is the output of the failed command:
FMM1162E
Failed to determine the online redo logs. Output of the failed command:output
FMM1163W
Script terminated with warnings.
FMM1164I
Renaming file system <old file system name> to <new file system name>
FMM1165I
Recovering the database database name.
FMM1166I
Switching LOGRETAIN and USEREXIT off for database database name.
FMM1167I
Creating relocate configuration file for database database name.
FMM1168I
Creating the storage path directories for database database name.
FMM1169I
Relocating database partitions partition list of database database name.
FMM1170I
Cloning database database name.
FMM1171I
No rename required.
FMM1172I
Preparing recovery of database database name.
FMM1173I
Renaming database old database name to new database name.
FMM1174I
Checking the clone system status of the database database name.
FMM1175I
Successfully checked the clone system status of the database database name.
FMM1176I
Restore control file file name.
FMM1177I
Performing media recovery.
FMM1178I
Opening the clone instance instance name.
FMM1179I
Function 'function name' does not consider the post-processing configuration file.
FMM1180I
Function 'function name' does not consider the pre-processing configuration file.
FMM1181I
Executing script type script 'script name'.
FMM1182I
Script terminated successfully.
FMM1183E
The parameter 'keyword' must have a length of 'length' characters."
FMM1200E
Profile parameter 'keyword' is set to YES but freeze/thaw is not supported by the underlying file system.
FMM1201E
There are no IBM Tivoli Storage Manager-Servers available.
FMM1202E
You must specify either MAX_SESSIONS, or all three specific session options(blank)(MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS, and MAX_RESTORE_SESSIONS).
FMM1203E
Not enough sessions available (sessions required and max_sessions available).
FMM1205E
If you want num_redo REDOLOGCOPIES you should give me at least num_mc different Archive Management Classes.
FMM1206W
If you want num_redo REDOLOGCOPIES you should give me at least num_mc different Archive Management Classes.
FMM1207E
Directory backup not supported.
FMM1208W
Retrying object: 'file name'. Retry count: [retry_num].
FMM1209E
Object not found or not accessible: 'objectname'.
FMM1210E
Input file not found or not accessible: 'file name'.
FMM1211E
There is something wrong with your CONFIG_FILE 'file name'.
FMM1212W
The file 'file name' is not found in the manual sorting file.
FMM1213E
The value 'wrongvalue' of the keyword 'keyword' is not allowed if 'dependentkeyword' is set to 'dependendvalue'."
FMM1214E
Error for session to server server name: error text
FMM1215I
Average transmission rate was gb per hour GB/h (mb per second MB/sec).
FMM1216E
There are no backup management classes available.
FMM1217E
There are no archive management classes available.
FMM1218E
Environment variable TEMP not set
FMM1219E
The paths of the disks found in the ASM instance indicate that the Oracle ASMLib is not used. This setup is currently not supported.
FMM1220E
The execution of the system command 'syscommand' ended with a return code other than 0. The output of the command was: 'commandoutput'.
FMM1221E
The parameter 'keyword' must have a value other than 'value' to be able to execute a mount operation.
FMM1222E
Version mismatch error. Please check setup (version_1:version_2).
FMM1223W
A Problem occurred during send of performance data to the Administration Assistant.
FMM1224W
Unable to initialize connection to Administration Assistant.
FMM1227I
Average compression factor was number.
FMM1228W
Server server name can not be used with password access method GENERATE in this environment. The process is running with user ID userid but the effective user ID is userid effective.
FMM1229E
Value for parameter BUFFSIZE (actual cur_number, maximum max_number) is too large for BUFFCOPY mode PREVENT.
FMM1230E
The following file was not processed: path.
FMM1231E
Maximum number of retries for file filename exceeded.
FMM1232I
Executing operation 'operation' on host 'host name'.
FMM1233I
Operation 'operation' completed.
FMM1234E
The directory 'directory' containing the XPYV components of the installation is missing.
FMM1235E
Logical volume 'logicalvolume' not available on system.
FMM1236E
The section DB2STANDBY is missing from the profile.
FMM1237E
Unable to perform mount request. The requested mount point 'mountpoint' is already in use.
FMM1239W
Logical volume 'logicalvolume' of volume group 'volumegroup' contains unmounted filesystem.
FMM1240E
Unable to mount the following filesystems: mointpoints
FMM1241E
Unable to unmount the following filesystems: mointpoints
FMM1242E
Error while parsing the profile: It is not allowed to have an ORACLE section without a CLIENT section.
FMM1243E
Only a single device class name is allowed for the profile parameter parameter in combination with the keyword keyword.
FMM1244E
The DB2 alias 'alias' could not be found in the database directory. Please check the value of the profile parameter parameter.
FMM1245E
There is no mount agent suitable for cloning with device class 'device class' started. Function cloning requires a dedicated mount agent that was limited to a specific device class using the option '-s <device class>'.
FMM1246E
The database name has to have specified, because multiple databases have been found within this instance.
FMM1247E
A FlashCopy Backup is not allowed because FlashCopy Clone(s) 'clones' is/are active with FlashCopy Type NOCOPY.
FMM1248E
A FlashCopy Clone with FlashCopy Type NOCOPY is not allowed because FlashCopy Backup(s) 'backups' is/are active.
FMM1249E
The LUN's of the datastores requested for backup are spread across multiple storage subsystems. IBM Tivoli Storage FlashCopy(R) Manager can support LUNs from only one storage subsystem.
FMM1250I
The 'user name to log-in to the file server' ID is connecting to the following file server: 'remote hostname of the file server' .
FMM1251I
A snapshot is taken for the following volume: 'name of the volume'.
FMM1252I
Deleting snapshot 'name of the snapshot to delete' for volume 'name of the volume'
FMM1253E
The 'target instance uuid' target instance UUID that is specified in the input file cannot be found or the UUID is assigned to a template. Edit the input file and specify a valid target instance UUID.
FMM1254I
The 'snap name' snapshot of the fileset 'fileset name' in the 'file system device name' file system was created.
FMM1255E
The process cannot continue. Reverting changes.
FMM1256I
The 'snap name' snapshot of the fileset 'fileset name' in the 'file system device name' file system was restored.
FMM1257E
The file server does not recognize the volume with the following serial number: 'identifier'.
FMM1258I
The following volume is offline: volume name
FMM1259I
The following clone volume already exists: volume name
FMM1260E
The GPFS file system 'device name' is currently mounted on the system at: 'current mount point'. The GPFS file system must be mounted at: 'default mount point', the default mount point.
FMM1261E
Key value set for undefined key column key_value. Command was: command
FMM1262W
The snapshot snapshot_name of the file system filesystem_name cannot be deleted because the file system is not known to the local cluster.
FMM1263W
The snapshot snapshot_name of the file system filesystem_name cannot be deleted because the file system is not mounted.
FMM1264W
The snapshot snapshot_name of the file system filesystem_name cannot be deleted. Error information: error_information
FMM1265W
The filesystem_name file system is unknown to the local cluster. Therefore, IBM Tivoli Storage FlashCopy(R) Manager cannot run the reconciliation process for the following snapshots: list_of_snapshots
FMM1266W
The filesystem_name file system is not mounted. Therefore, IBM Tivoli Storage FlashCopy(R) Manager cannot run the reconciliation process for the following snapshots: list_of_snapshots
FMM1267W
IBM Tivoli Storage FlashCopy(R) Manager cannot determine whether the snapshot snapshot_name snapshot of the file system filesystem_name is still available. Error information: error_information
FMM1268E
A relative file name 'file name' was found in the infile. Relative file names are not supported.
FMM1269E
For GPFS snapshots, the value parameter value is not valid for the parameter name parameter.
FMM1270I
The following volume is mapped to initiator group: volume name.
FMM1271I
The following volume is online: volume name
FMM1272E
The following VMs listed in the instant restore input file are not part of the backup: vms_in_infile
FMM1273E
The source volume with serial number cmd is not attached to any known ESX hosts.
FMM1274E
The file system filesystem_name cannot be mounted. If the file system is to be mounted remotely, ensure that the mounting cluster has the correct permissions to mount the file system. Additional information: command_and_command_output
FMM1275E
The 'vm_name' virtual machine is located on the following data stores : list_of_datastors. In the input file not all of these data stores were specified. You must specify all listed data stores in the input file or exclude this virtual machine so that the instant restore can continue.
FMM1276E
Cluster cluster_name cannot mount the file system filesystem_name in read/write mode. If the file system is to be mounted remotely, ensure that the mounting cluster has the correct permissions to mount the file system in the mode requested.
FMM1278W
The power on VM task for VM 'vmname' failed.
FMM1279E
The 'volume name' LUN cannot be mapped by using the initiator group 'initiator group': error message
FMM1280E
The mapping for the 'volume name' LUN cannot be removed by using the initiator group 'initiator group': error message
FMM1283E
The file file name is listed in the backup infile but is not on a GPFS file system. The backup operation cannot continue.
FMM1284E
The operation instant restore cannot be started for backup with id 'backupid' due to the FlashCopy backup is still copying data in the storage system from source to target.
FMM1285I
A GPFS shadow database is missing in path path. IBM Tivoli Storage FlashCopy(R) Manager will request rebuilding of one or more required shadow databases.
FMM1286I
GPFS command mmbackup for path directory ended with exit code exit code. IBM Tivoli Storage FlashCopy(R) Manager is retrying the operation. Retry count count of maximum number of retries.
FMM1287I
IBM Tivoli Storage FlashCopy(R) Manager is requesting a full backup for path directory because there is no inventory data available for any specified TSM server.
FMM1300E
Directory ${REPLACE_DIRECTORY_STRING} is not a shared directory on the specified node.
FMM1301E
Failed to create a link to a shared directory.
FMM1493I
Back-End Capacity Report: Number of managed objects: number_of_objects
FMM1494I
Logical Unit (LUN) Capacity Report: Number of managed objects: number_of_objects
FMM1495I
Logical Unit (LUN) Capacity Report: Total protected size: size
FMM1496I
Back-End Capacity Report: Total protected size: size
FMM1497I
Front-End Capacity Report: Number of managed objects: number_of_objects
FMM1498I
Front-End Capacity Report: Total protected size: size
FMM1501E
Only one LUN per ASM failure group is allowed with DS8000 storage. 'LUN count' LUN's have been found in failure group 'failure group name' of diskgroup 'diskgroup name'.
FMM1502E
Oracle ASM with SVC is not supported with the setting 'profile_value' for the profile parameter 'profile_param'.
FMM1503E
The single disk restore operation to the source virtual machine 'vm name' with instance UUID 'source vm instance uuid' is not possible since 'number snapshots' VMware(R) snapshots have been found on the source virtual machine but none are allowed.
FMM1504E
The single disk restore operation of the virtual machine 'vm name' with instance UUID 'source vm instance uuid' is not possible since 'number snapshots' VMware(R) snapshots have been found for this virtual machine as it is contained in the backup but none are allowed.
FMM1505E
Operation aborted because a different operation by this database client is already running.
FMM1506E
Error: 'description' on host 'hostname' while executing command 'command'.
FMM1507E
The process needs to run with root authority.
FMM1508E
The service service_name has terminated due to a previous error. Please check all logs for additional information.
FMM1509E
Authentication failure. The password specified is not authorized for accessing component. Please verify that the passwords specified in the password files on the different production and backup/cloning systems are correct.
FMM1510I
New connection received from host hostname.
FMM1512E
An error occurred during shutdown: Error information
FMM1513I
*****> Database client connected: instance instance, database database_namepartition_numbernodename
FMM1514I
*****> Device client connected.
FMM1515I
Client is logging to file_name
FMM1516I
Deleting container container.
FMM1517I
Deleting target data container defined by container_description.
FMM1518E
Internal error: The system is trying to use the same device agent, although the synchronization mode is not PARALLEL.
FMM1519E
A failure occurred during initialization of one or more of the nodes participating in this operation. Please check the logs for more information.
FMM1520E
Volume volume_name is shared across partitions. Volume sharing is not allowed.
FMM1521I
Retaining number backups
FMM1522E
The requested meta-information (subject="description") is not available.
FMM1523W
Warning: The following containers were reused without being explicitly released: description
FMM1525E
The process service_name is in an inconsistent state. Please check for previous errors and restart the process afterwards.
FMM1526E
A configuration file (profile) must be provided.
FMM1529E
The device 'device_type' is not supported by the wizard.
FMM1530E
Failed to launch the device agent for device_type. Please consult your user documentation to make sure that all requirements for the specified device are met.
FMM1534E
Unexpected version actual_version of the repository located at path. Expected version: supperted_version
FMM1535E
Unexpected characteristics (bitwidth=bitwidth repository) of the repository located at path. Expected bitwidth: bitwidth expected
FMM1536E
The repository located at path is not valid.
FMM1537E
The repository located at path was written with an incompatible protocol (protocol_version incompatible). Expected protocol: protocol_version expected
FMM1538E
Unexpected repository type. The path 'path' does not point to a repository of type "protocol_type".
FMM1539E
Root privileges required. Could not change user ID to root.
FMM1540E
/etc/inittab entries are limited to 127 characters. Please consult your user documentation for information on manually completing the installation procedure.
FMM1541E
/etc/inittab was not updated because some of the processes have apparently been added. Please re-run the setup after calling the setup script with option '-a disable' if you want to change to a standard setup.
FMM1542E
Failed to uninstall because some of the processes to be uninstalled are still listed in /etc/inittab. Please re-run the setup after stopping the component by calling the setup script with option '-a stop'.
FMM1543E
The component is still referenced within the /etc/inittab. In order to terminate the component re-run the setup script with option '-a stop'.
FMM1544E
New entries cannot be added to /etc/inittab because it already contains too many entries starting with 'ac'. Please refer your user documentation for a manual setup of this package.
FMM1545E
oldprod is currently running.
FMM1546E
IBM product name was not started.
FMM1547E
Failed to remove the data associated with the deleted backup backup_id.
FMM1548E
Failed to monitor the data associated with the deleted backup backup_id.
FMM1549E
Failed to load component_name
BKI1550W
Unable to perform background monitoring for backup 'backup id' for time.
FMM1553I
Component_name is logging to path
FMM1554W
The agent 'component_name' terminated with exit code number.
FMM1555I
Profile successfully created.
FMM1556E
Some data of backup backup_id are unavailable. It is impossible to restore the data requested.
FMM1557I
Device client is logging to path
FMM1558E
There are no mount agents registered for participant(s) participant_list
FMM1561E
Profile name profile_name does not point to a file.
FMM1562E
Deleting the backup as requested is impossible while any part of it is mounted.
FMM1563I
The snapshot backup defined by timestamp timestamp for instance instance, database database_name, and partition partition_number cannot be restored.
FMM1564W
Backup id is marked for deletion. You need to unmount before it can be physically deleted.
FMM1567I
Reconciliation for device class 'device class' completed successfully.
FMM1568I
Removing backup backup_id from the repository because it has not been found on the storage device during reconciliation.
FMM1569I
Updating backup backup_id in the repository because some data was not found on the storage device during reconciliation.
FMM1570W
The following container could not be deleted from the storage box during reconciliation: volume_name.
FMM1571W
The specified value for 'recon_interval' is 0. Be aware that every time a background monitor is started a reconcile will be scheduled so that other background operations will never be scheduled. This should be used for testing purposes only.
FMM1572I
Starting reconciliation for device class 'device_class_name'
FMM1573I
The container 'volume_name' has been successfully deleted from the storage box. It didn't belong to any backup in the repository.
FMM1574I
Backup for hardware isolation key is created using DEVICE_CLASS device class.
FMM1575E
product name cannot be used to perform dual backups. Update your profile to perform either a disk-only backup or use TSM for ERP to perform a dual backup.
FMM1576W
The backup backup id is skipped from expiration processing because it is mounted.
FMM1577W
The backup backup id is skipped from expiration processing because a mandatory Tivoli Storage Managerbackup from this image is pending.
FMM1578W
A backup is skipped from expiration processing because of the following error:
FMM1579E
Failed to find a suitable target set for device class device class.
FMM1580E
Specifying a target volume serial number is mandatory for parameter 'TARGET_VOLUME'.
FMM1581E
Error while parsing parameter TARGET_VOLUME target volume param in volumes file: the parameter TARGET_VOLUME allows at most three parameters.
FMM1582I
The target set target set will be used for the current backup.
FMM1583W
Backup agents were requesting incompatible IBM Tivoli Storage Manager backup options. The composed states are: 'states'.
FMM1584E
Snapshot backup referenced by ID 'backup id does not exist.
FMM1586E
Not enough sessions available.
FMM1588E
The master password you provided does not meet the minimum complexity requirements. Acceptable master passwords are a minimum of minlength characters and must contain at least one number and one letter.
FMM1999E
A restore operation is not allowed for a backup that was originally performed with FLASHCOPY_TYPE NOCOPY from target volume targetVolume on San Volume Controller Version version.release.revision. Use San Volume Controller Version 5.1 or later.
FMM2000I
Successfully connected to component_name on port portnumber.
FMM2001E
Socket error while connecting to component_name at host: reason.
FMM2002E
The group permissions of the user 'username' are not sufficient. The Oracle(R) executables have the group ownership 'group' but the specified user does not belong to that group.
FMM2003I
File file_name BID deleted.
FMM2004E
Socket error while listen to port port number - error: error text.
FMM2005W
The virtual machine 'vm name' with instance UUID 'source vm instance uuid' will be processed without the requested backup mode since the 'device names' devices are directly passed through to the virtual machine.
FMM2006W
The virtual machine 'vm name' with instance UUID 'source vm instance uuid' will be processed without the requested backup mode since fault tolerance is turned on.
FMM2007E
Unknown Port: port
FMM2008E
Unable to connect to component_name.
FMM2009I
Deleting backup version_number and all older backups.
FMM2010E
Error occurred processing FRONTEND.
FMM2011E
Error occurred processing BACKEND.
FMM2012E
The specified user name or password is not correct, authentication failed.
FMM2013I
Starting FRONTEND program.
FMM2014I
FRONTEND program finished.
FMM2015I
Starting BACKEND program.
FMM2016I
BACKEND program finished.
FMM2017I
Blocksize is set to num_bytes bytes
FMM2018I
The file system 'file system' was added successfully to the remote cluster 'remote cluster name'.
FMM2019I
The snapshot of file system 'file system' was mounted successfully to 'path'.
FMM2020I
The file system 'file system' was removed successfully from remote cluster 'remote cluster name'.
FMM2021I
The file system 'file system' was unmounted successfully.
FMM2022E
Unable to change mode of file file name: description
FMM2023I
The 'vm name' virtual machine with the 'vm instance uuid' instance UUID is resumed.
FMM2024E
Error in connection to component_name.
FMM2025E
Failed to respond to a message received from component_name.
FMM2026E
Unexpected exception in handler: handler.
FMM2027I
Using TSM-API version your API version (compiled with compiled with version).
FMM2028W
Unable to terminate a session due to the following error:session.
FMM2029E
Could not instantiate the buffer allocator because of the following incompatibility issue: expression.
FMM2031E
A buffer allocator cannot simultaneously satisfy all of the following properties:list of properties
FMM2033E
Cannot instantiate allocator of type allocator type with the following additional properties:list of properties
FMM2086W
The following failure groups were not needed during the backup: serial. Either they are misspelled in the profile or they are not online. You might want to check them.
FMM2087W
The diskgroup 'dg' contains 'fg total' failure groups, but currently only 'fg online' of them are online. Just the online failure groups can be included in the backup. During restore just the online failure groups would be restored and the others would be dropped.
FMM2088I
The diskgroup 'dg' and its online failure groups: fg are now dropped.
FMM2089W
The diskgroup 'dg' contains failure groups which are currently offline: fg. The diskgroup cannot be dropped from these failure groups. Please ensure that they do not become available during the restore process.
FMM2090E
The device 'dev' could not be removed. Please ensure that you are not accessing the ASM or database instance for example by an open sqlplus console.
FMM2091W
For the virtual machine 'vm name' the backup mode mode is changed to ASIS because it has raw device-mapping disks attached. As a consequence, the backup of the specified virtual machine is only crash consistent.
FMM2092W
A restore of the virtual machine 'vm name' does not recover the existing VMware(R) snapshots because it has raw device-mapping disks.
FMM2093W
The virtual machine 'vm name' has raw device-mapping disks attached. When you restore this virtual machine from the hardware snapshot the achieved consistency level is crash consistency only. This limitation does not apply when you restore the virtual machine from the offloaded Tivoli Storage Manager backup.
FMM2094W
A file layout change was detected during the backup of the virtual machine 'vm name', this change was probably caused by a VMware(R) Storage VMotion operation. The virtual machine is excluded from the backup and cannot be restored from this backup.
FMM2095E
The backup is unusable because all the virtual machines that it contains have been invalidated due to an interfering VMware(R) Storage VMotion operation.
FMM2096W
The offload agent ('bexname') was not started. As a consequence, the snapshot backup is not automatically offloaded to IBM Tivoli Storage Manager.
FMM2913I
The version delete setting is configured to retain number backup generations. Checking for expired backups.
FMM4000W
The attributes of file 'file name' cannot be restored. Reason: errno(error_num) error_desc.
FMM4001E
File 'file name' cannot be created. Reason: errno(error_num) error_desc
FMM4002E
Error during write of file ' file_name'. Reason: errno(error_num) error_desc
FMM4003E
Operation mount will be aborted. Physical volume(s) with conflicting physical volume id(s) have been found on the target host 'host_name'list_of_pvids
FMM4005E
Error allocating memory block for file file name. BLOCKSIZE may be too large.
FMM4007E
File 'filename' cannot be read Reason: errno(error_num) error description
FMM4008E
File 'filename' cannot be opened. Reason: errno(error_num) error_text
FMM4009E
Not enough space to write File 'filename'. Possible reasons: disk full or ulimit exeeded.
FMM4010E
SAP requires the file filename to be a regular file.
FMM4011W
The backup device type (filetype backup devicetype backup devsubtype) differs from the restore device type (filetype restore descr1 descr2) for name.
FMM4012E
Unexpected EOF for file 'filename' after reading number Bytes.
FMM4013I
CreateFile() with dwFlagsAndAttributes='attribute'.
FMM4014E
File 'filename' cannot be accessed. Reason: errno<(number) errormsg
FMM4015E
Failed to attach the volumes 'volumes' to the host 'hostname'.
FMM4016W
The mapping between volume 'vol' and the host 'hostname' was not found in the CIMOM.
FMM4017E
Failed to detach the volumes 'volumes' from the host 'hostname'.
FMM4018E
Parameter parameter name requires a value in the range between min and max.
FMM4019E
The hostname 'hostname' must be defined as a host entry in the IBM SAN Volume Controller.
FMM4021E
The FlasCopy mapping for the source and target volumes 'src' and 'tgt' was found, however the consistency group is missing.
FMM4022E
The LUN serial numbers Lun serials that were used by the original datastore are now in use by the following datastores: new datastore names Ensure that the LUNs are not in use by other datastores, by removing the datastores that are conained by these LUNs from the vCenter Server.
FMM4023E
The new datastorename datastore, which was identified to be overwritten by the instant restore, does not use all the LUNs of the original datastore. Remove this datastore and corresponding virtual machines from the vCenter Server and retry the instant restore operation again.
FMM4024E
This backup version was created with a previous version of the product that does not support datastore restore (instant restore). Create a new backup to enable the instant restore function. You can restore the backup by using a virtual machine restore operation.
FMM4175E
San Volume Controller VDisk vdisk is not online. Please retry this command after bringing this volume back online.
FMM4176E
A restore is not allowed from space-efficient target volume targetVolume on San Volume Controller Version version.release.revision. Use San Volume Controller Version 5.1 or later.
FMM4177E
User specified copy type usrCopyType is in conflict with the copy type fcCopyType for the previously established FlashCopy. Please retry the operation for this copy type specifying a different target set.
FMM4178E
The directory 'directory' containing the CIM components is missing.
FMM4179E
Metro mirror or global mirror remote copy relations for source 'source vdisk' do not have a consistency group defined.
FMM4180W
The current number of metro mirror or global mirror remote copy relations 'current num of rc relations' is different from the number at the time of backup 'original num of rc relations'.
FMM4183I
Performing flashcopytype FlashCopy of source volume source to target volume target.
FMM4184I
CIM Agent version for hwType: 'version.release.revision'.
FMM4185E
The mandatory source and target FlashCopy mapping source / target cannot be satisfied because the volumes do not match.
FMM4186E
For the sources source no matching target LUN could be found in the selected target set.
FMM4187E
The LUN with serial number 'serial' is not known by the configured CIM Agent 'primaryserver' of storage system type 'hardwaretype'.
FMM4188E
The target volume named volname is not known by the CIM Agent in the cluster cluster.
FMM4189E
The cluster id clustername; specified by the parameter parname; is not known by the CIM Agent.
FMM4190I
All source/target pairs are in an incremental FlashCopy relation.
FMM4191I
No source/target pairs are in an incremental FlashCopy relation.
FMM4192I
Not all source/target pairs are in an incremental FlashCopy relation.
FMM4193E
The DB2 instance owner instanceowner could not be found in /etc/passwd.
FMM4194I
All virtual machines that are located within the 'datastore name' data store are powered down and unregistered.
FMM4195I
The 'vm name' virtual machine is successfully restored and registered at the 'ESX host name' ESX host.
FMM5000E
IBM Tivoli Storage Manager Error:error_message
FMM5001E
IBM Tivoli Storage Manager Error:error_message
FMM5002E
IBM Tivoli Storage Manager Error during inquire of mux file backup_id:error_message
FMM5003E
IBM Tivoli Storage Manager Error:error_message
FMM5004W
IBM Tivoli Storage Manager Error:error_message
FMM5005E
IBM Tivoli Storage Manager Error.
FMM5006E
IBM Tivoli Storage Manager Error:error_message
FMM5007E
IBM Tivoli Storage Manager Error.
FMM5008E
IBM Tivoli Storage Manager Error.
FMM5009E
IBM Tivoli Storage Manager Error:error_message
FMM5010E
IBM Tivoli Storage Manager Error:error_message
FMM5011E
IBM Tivoli Storage Manager Error:error_message
FMM5012E
Cannot open IBM Tivoli Storage Manager API message text file. Check if DSMI_DIR is set correctly. Current value of DSMI_DIR is: dsmi dir
FMM5013E
Value for name is too long. Current value: value
FMM5014E
IBM Tivoli Storage Manager Error:error_message
FMM5015W
Data description, file name could not be restored, because it was backed up with a newer version (objInf_support information).
FMM5016I
Time: current time New TSM session created: management class: management_class, server: server_name, type: session_type
FMM5017E
Internal IBM Tivoli Storage Manager Error: Transaction succeeded although it was expected to fail.
FMM5018E
The requested buffer has a size (current_size bytes) that is smaller than requested requested_size.
FMM5019E
Error during delete of object filename:object
FMM5020E
Error while deleting objects :objects
FMM5021W
No data is deleted on the TSM Server because the environment variable "XINT_FUNCTION_DELETE" is set to "DISABLE".
FMM5022W
Error during version delete. Not all backups that should have been expired could be removed.
FMM5637I
SAN Volume Controller CIM Agent version is: version.msgnl;
FMM5651E
Incorrect copy type copyType has been specified for space-efficient target volume targetVolume. Please retry this command using NOCOPY copy type.
FMM5655E
The value you specified is not a directory.
FMM5667E
A Flashcopy Restore operation is in progress between source volume sourceVolume and target volume targetVolume. Please retry this command after the restore operation completes.
FMM5668E
The input target volume targetVolume is already in a flashcopy relationship with a volume other than the input source sourceVolume. Please retry this command with a different target volume.
FMM6199E
Failed to determine the database id. Output of the failed command:output
FMM6201I
Checking status of database.
FMM6202E
The log mode for this database is NOARCHIVELOG.
FMM6203E
The Oracle database is currently in read-only mode.
FMM6204E
The Backup type is online but the mount mode is either nomount or startup restricted.
FMM6205I
Changing Oracle mode to: mode.
FMM6206E
No table space was found for the Oracle database.
FMM6207E
Oracle database data files were not found. More details: errormsg
FMM6208E
Oracle database control files were not found.
FMM6209E
The database failed to shutdown during the flashcopy operation.
FMM6210E
Failed to open the output file: filename
FMM6211E
Failed to copy the database controlfile. Please check log file 'filename'.
FMM6212I
Suspend database.
FMM6213E
An error occurred while attempting an 'alter system suspend' action. More details: errormsg
FMM6214I
Resume database.
FMM6215E
An error occurred while attempting an 'alter system resume' action. More details: errormsg
FMM6216E
Failed to get Oracle version information.
FMM6217I
Database switched to next logfile.
FMM6218E
Backup ID to delete not specified.
FMM6219I
Backup to Tivoli Storage Manager: filename
FMM6220E
Another clone with clone database name 'clone database name' is already mounted on a clone server using device class 'device classes'.
FMM6221I
Database profile: filename
FMM6222E
Database profile 'filename' not found.
FMM6223I
Detected control file: filename
FMM6224I
Create control file copy: control file
FMM6225I
Create database parameter file 'filename' from SPfile.
FMM6226E
Default directory for database parameter file 'filename' not found.
FMM6227I
Parameter 'database_control_file_restore' is set to yes in the profile. You will need to do the incomplete recovery after the restore.
FMM6228E
The database seems to be running. Restore not possible.
FMM6229I
Restoring control file controlfile
FMM6230I
Set table space files in backup mode.
FMM6231I
End backup mode for table space files.
FMM6232I
Looking for the latest backup.
FMM6233I
Restoring backup with ID id.
FMM6234E
No backup found which could be restored.
FMM6235I
Deleting backup with ID id.
FMM6236E
Failed to delete backup with ID id. Reason: reason
FMM6237E
Backup failed. Please check RMAN log.
FMM6238E
Failed to switch logfiles. This is the output of the failed command:output
FMM6239E
Failed to detect read mode. This is the output of the failed command:output
FMM6240E
Failed to create a pfile from spfile. This is the output of the failed command:output
FMM6241E
The tablespace file 'filename' is a link but not a real file.
FMM6242E
Raw devices are not supported. ('devicename')
FMM6243E
Failed to excute sql cmd 'command' on host 'hostname'. This is the output of the failed command:output
FMM6244I
Received an information message from the adapter:info_message
FMM6245I
source volume ID: serialnumber capacity: size
FMM6246I
Total managed capacity: size
FMM6247W
No serial number has been found for device: devicename
FMM6248W
No device has been found for the character device 'devicename' with major number 'major' and minor number 'minor'.
FMM6249W
The diskgroup 'dg' contains failure groups which are currently offline: fg. These failure groups cannot be included in the flashcopy.
FMM6250E
Error during initialization: descritpion
FMM6251E
Error during start of backup: description
FMM6252E
Error during partitioning: description
FMM6253E
Error during preparation of snapshot: description
FMM6254E
Error during creation of snapshot: description
FMM6255E
Error during verification of snapshot: description
FMM6256E
Error during write of meta-information: description
FMM6257E
Error during retrieval of meta data: description
FMM6258E
Error during query-initialization: description
FMM6259E
Error during retrieval of query information: description
FMM6260E
Error during end of query: description
FMM6261E
Error during start of restore: description
FMM6262E
Error during restore: description
FMM6263E
Error during end of restore: description
FMM6264E
Error during start of delete: description
FMM6265E
Error during end of delete: description
FMM6266E
Restoring Oracle control files failed. Oracle control files are on raw volumes in the production server and those are supposed to be created manually on the backup server. It failed because of either control files are not created on the backup server or created incorrectly. Please check log file 'filename'.
FMM6267E
Restoring Oracle control files failed. Please check log file 'filename'.
FMM6268W
The lun 'lunname' of failure group 'failuregroupname' has not been found on the storage device.
FMM6269I
The diskgroup 'diskgroupname' with 'redundanctype' redundancy and 'failuregroupnumber' failure groups has been partitioned with failure groups 'failuregroupnames'.
FMM6270E
INFILE name is required.
FMM6271W
Specified partition(s) 'partition list' already offloaded to Tivoli Storage Manager.
FMM6272I
Update snapshot backup with ID 'snapshot backup ID'.
FMM6273E
Valid usability state values are 'yes' or 'no'.
FMM6274E
Operation failed because a resource is temporarily unavailable. Please restart the operation.
FMM6275E
The requested process can currently not be started.
FMM6276E
Another mount agent service is currently running.
FMM6277E
Partition 'partition number' is already handled by the mount agent instance running on 'hostname'.
FMM6278E
No mount agent on a backup server is set up to handle partition 'partition number' within the current operation. Make sure that the mount agent is started correctly and verify that the hostnames listed in db2nodes.cfg match with the hostname of the backup server. If the hostnames do not match, start the mount agent with the -H hostname option.
FMM6279E
No mount agent is setup on a backup server to handle the current operation. Make sure that the mount agent is started correctly.
FMM6280E
A usability state argument is missing.
FMM6281E
The usability state 'state' is unknown or not supported.
FMM6282E
query archive unsuccessful.
FMM6283E
offloaded tape backup unsuccessful.
FMM6284W
offloaded tape backup successful with warnings.
FMM6285I
Start saving file number files ...
FMM6286E
The clone database name 'cloneSID' has been specified multiple times in the profile. Please check the values of the keyword 'keyword'.
FMM6287E
The keyword 'keyword1' instead of 'found_keyword' is needed for the keyword 'keyword2'."
FMM6288E
The command line option -s <DEVICE_CLASS> is not allowed for function function name.
FMM6289I
The 'datastore name' data store was successfully added to the 'ESX host name' ESX host.
FMM6290I
The 'datastore name' data store was successfully unmounted from the 'ESX host name' ESX host.
FMM6291E
One or more Oracle control files are located outside ASM disk groups.The following Oracle control files are not located within ASM disk groups: control file names
BKI6292E
The Oracle version of this database, version number, does not meet the required version, 11gR2, for ASM database cloning with a SID different from the source database.
BKI6293E
You cannot rename the ASM disk group disk group name as it is still mounted.
BKI6294E
Execution was stopped. ASM disk group name disk group name on a clone system will exceed 30 bytes limit.
FMM6295E
Unable to rename disk group old disk group name to new disk group name because a disk group with the new name exists already.
FMM6296E
IBM Tivoli Storage Manager does not back up multitenant container databases (CDB) or pluggable databases (PDBs).
FMM6501I
Initializing 'function' request.
FMM6502I
Executing 'function' request.
FMM6503I
Terminating 'function' request.
FMM6504E
The 'function' request failed.
FMM6505E
Forced 'function' requires the instance, database, and backup ID filter arguments.
FMM6506I
Backup backup id was created with option TSM_ONLY. It is marked for deletion after the first TSM backup attempt.
FMM6507E
Function 'function' is not supported.
FMM6508I
Initializing partition(s) 'partitions(s)' of database 'database name' as type.
FMM6509E
Failed to initialize partition 'partition(s)' of database 'database name'.
FMM6510I
Partition(s) 'partition list' of database 'database name' initialized successfully.
FMM6511E
A backup-ID option must not be specified when starting the off-loaded backup.
FMM6512I
The 'function' request for database 'database name' with partitions (partition(s)) processed successfully.
FMM6513I
The resources of database 'database name' with partitions (partition(s)) are already mounted.
FMM6514E
The specified filter did not result in a match in the snapshot repository.
FMM6515E
A snapshot backup currently offloaded to tape is no longer mounted.
FMM6516E
Another 'function' request for a snapshot backup is already running.
FMM6517I
A snapshot backup is already mounted.
FMM6518I
No snapshot backup is currently mounted.
FMM6519I
There is no snapshot backup currently pending to be offloaded to tape.
FMM6520I
Starting database instance 'instance name'.
FMM6521I
Database instance 'instance name' was started successfully.
FMM6522W
Database instance 'instance name' already started.
FMM6523E
Database instance 'instance name' could not be started.
FMM6524I
Stopping database instance 'instance name'.
FMM6525I
Database instance 'instance name' was stopped successfully.
FMM6526W
Database instance 'instance name' already stopped.
FMM6527E
Database instance 'instance name' could not be stopped.
FMM6528E
The file containing the list of partitions and hosts to be off-loaded could not be created.
FMM6529I
Database instance 'db instance' already started.
FMM6530E
The default database path could not be determined.
FMM6531I
Cataloging database 'database name' on path 'path'.
FMM6532I
Database 'database name' on path 'path' cataloged successfully.
FMM6533E
Failed to catalog database 'database name' on path 'path'.
FMM6534E
A snapshot backup is already mounted.
FMM6535E
The snapshot backup with ID 'identifier' does not qualify for restore operations.
FMM6536W
The 'vm name' virtual machine is ignored and cannot be part of the backup since it is not connected to the vCenter server.
FMM6537I
Database 'database name' on path 'path' already cataloged.
FMM6539W
The retry threshold for the snapshot backup was exceeded.
FMM6540I
Start time: Starting backup of database 'database name', partition(s) 'partition(s)' with the following options: METHOD offload backup method SESSIONS number of sessions OPTIONS options BUFFERS number of buffers BUFFERSIZE buffer size PARALLELISM degree of DB2 parallelism
FMM6541I
End_time Instance Database Partition Snapshot_ID Tape_backup_ID
FMM6542I
end timeinstance namedatabase namepartitionsnapshot idtape backup id
FMM6543E
The disks could not be attached to the requested target virtual machine: 'vm name'. Please make sure to use the ESX host where the target virtual machine is running as auxiliary ESX host. ESX host 'esx hostname' has been used for this operation.
FMM6544I
Snapshot backup suspend time: suspend time
FMM6545I
Write control file ctrlfile
FMM6546I
Write database parameter file parameter file
FMM6547I
Do not overwrite database parameter file.
FMM6548I
Start backup of database instance 'instance'.
FMM6549I
Finished backup of database instance 'instance' successfully.
FMM6550I
Resetting the database logs to prepare the change of the database id.
FMM6551I
Changing the database id. This will stop the database.
FMM6552I
Successfully changed database id from old database id to new database id.
FMM6553E
Failed to changed database id. This is the output of the failed command:error output
FMM6554E
The original virtual machine with instance UUID 'target instance uuid' is needed for this single disk restore operation but was not found. Please specify a target virtual machine.
FMM6555I
Selected snapshot backup with ID 'id'.
FMM6556E
Failed to retrieve meta data.
FMM6557I
The 'function' request for database 'dbname' processed successfully.
FMM6558I
The resources of database 'dbname' are already mounted.
FMM6560E
Backint could not be found at 'directory'.
FMM6561W
Failed to initialize partition 'partition(s)' of database 'database name'. Restore remaining partitions.
FMM6562I
Changing the database shared memory of partition(s) 'partitions(s)' of database 'database name' to size.
FMM6563E
Failed to change the size of the database shared memory of partition 'partition(s)' of database 'database name'.
FMM6564I
Successfully changed the size of the database shared memory of Partition(s) 'partition' of database 'database'.
FMM6565E
Another operation of IBM Tivoli Storage FlashCopy(R) Manager is preventing accesss to this backup.
FMM6566E
The 'option' option is not supported by the 'function' operation.
FMM6567E
More than one database is in the database instance 'instance_name'. Specify the name of the database to be processed via the '-d' option of script 'fcmprereqchecker.sh'.
FMM6568E
The binary 'binary_name' was not found in the path of the user 'username'.
FMM6570E
The 'name' name is reserved. You must specify another name.
FMM6571E
When the system was trying to determine the database instance path, an error occurred: error_information Check whether the DB2 instance is set up correctly.
FMM6572E
Error code return_code was returned from shell command 'command'. Command output:command_output Output from shell:shell_output
FMM6573E
No valid application environment was discovered for the user 'user'.
FMM6574W
The task progress cannot be displayed or updated because the following problem occurred: error
FMM6575E
The file 'filename' is not located in an ASM disk group.
FMM6576E
Control file 'filename' is located in data file disk group 'diskgroup'.
FMM6577E
Redo log file 'filename' is located in data file disk group 'diskgroup'.
FMM6600E
Unexpected error during 'function'.
FMM6601W
The 'ds name' datastore with the 'vm names' virtual machines is ignored and cannot be part of the backup since it has the type type that is not supported.
FMM6602W
The virtual disk 'disk name' of the virtual machine 'VM name' exists in a type datastore that is not supported. This virtual machine will be excluded from the backup.
FMM6603W
The 'ds name' virtual machine is ignored and cannot be part of the backup since it is a placeholder entity that is managed by VMWare Site Recovery Manager (SRM).
FMM6604I
The tablespace format check verifies that all database tablespace formatting is supported by IBM Tivoli Storage FlashCopy(R) Manager.
FMM6606I
The following files do not belong to the application: file names The extra files must be added to the IBM Tivoli Storage FlashCopy(R) Manager negative list.
FMM6608E
The following tablespaces are not supported: tablespace names
FMM6609I
The extra-files check (fcm.extrafiles) verifies that only database-related files are located on the ASM database disk groups.
FMM6610I
The ASM instance check (fcm.is_asm_instance) validates if the database instance is an Oracle ASM instance
FMM6611I
The Disks on the same Storage Type check (fcm.same_storage_type) validates if the disks where the database is stored, are located on a single type of Storage System.
FMM6612E
The disks where the database is stored are located on different types of storage systems: Storage System Types List
FMM6613E
The disk where the database partition partition is stored are on different types of storage systems as follows: Storage System Types List
FMM6614I
The Disks on the same Storage Device check (fcm.same_storage_device) validates if the disks where the database is stored, are located on a single Storage System.
FMM6615E
The disks where the database is stored are distributed over more then one storage system. List of Storage System IDs: Storage System ID list
FMM6616E
The disks where the database partition partition is stored are on different storage systems: List of Storage System IDs: Storage System Types List
FMM6617W
The Disks on the same storage device check (fcm.same_storage_device) cannot be run for non-IBM and N-Series storage devices. In these cases, this check must be run manually. For information about this check, see the Pre-Installation Checklist PDF.
FMM6618E
The disks where the ASM failure group failure group included in ASM diskgroup Diskgroup are stored, are on different types of storage systems as follows: Storage System Types List
FMM6619E
The disks where the ASM failure group failure group included in ASM Diskgroup Diskgroup are stored, are distributed over more then one storage system as follows: Storage System Types List
FMM6620E
The disks where the ASM diskgroup Diskgroup are stored, are distributed over more then one storage system as follows: Storage System Types List
FMM6621E
The disks where the ASM diskgroup Diskgroup are stored, are on different types of storage systems as follows: Storage System Types List
FMM6622E
No database was found in instance 'instance name' owned by 'user'.
FMM6801E
DB2 Library not specified
FMM6802E
Failed to load DB2 library 'library name'dlopen error: dlopen error
FMM6803E
DB2 Library 'library name' could not be loaded.
FMM6804E
DB2 Library symbols 'library name' could not be loaded: rc _ return code
FMM6805I
The production TCP/IP node 'tcp node' will be cataloged.
FMM6806E
Unable to catalog production TCP/IP node 'tcp node' as 'node alias'.
FMM6807I
The production TCP/IP node 'tcp node' has been cataloged successfully as 'node alias'.
FMM6808I
The production database 'database name' will be cataloged.
FMM6809E
Unable to catalog production database 'database name' as 'new database name'.
FMM6810I
The production database 'database name' has been cataloged successfully as 'new database name'.
FMM6811E
Parsing error in file 'filename' at line 'line number' at position 'position'. Expected one of 'valid possibilities' but found 'line'.
FMM6812E
Unable to connect to the production database 'database name'.
FMM6813E
Unable to disconnect from the production database 'database name'.
FMM6814I
A attachment to the production database instance 'database instance' has been made.
FMM6815I
A connection to the production database 'database name' has been made.
FMM6816I
TBS container name=tablespace container name
FMM6817E
Tablespace container 'tablespace container name' is in exception state.
FMM6818I
Set client connection to Node 'node number'.
FMM6819E
No data was obtained from Database Monitor.
FMM6820E
The 'hostname' ESX server has not been found in the vCenter server.
FMM6821E
Attachment to the production DB2 instance for user user failed.Verify that the database manager on the production system has started.
FMM6822E
Some tablespace containers are in an exception state.
FMM6823I
The attachment to the production database instance 'database instance' has been detached.
FMM6824I
The connection to the production database 'database name' has been disconnected.
FMM6825E
A DB2 API call failed with the following error: error code
FMM6826E
DB2 Library 'library name' could not be unloaded.
FMM6827E
Tablespace 'tablespace' is in state 'state'. Snapshot backup is not possible.
FMM6828E
Some tablespaces are not in 'NORMAL' state. Snapshot backup is not possible.
FMM6829I
Connecting to the production database 'database name' ...
FMM6830I
Disconnecting from the production database 'database name' ...
FMM6831I
Attaching to the production database instance 'database instance' ...
FMM6832I
Detaching from the production database instance 'database instance' ...
FMM6833E
The RMAN executable was not found or is not executable by the current user. Could not verify the connection to the Oracle catalog database.
FMM6901I
Response to Init request.
FMM6902I
Response to Partition request.
FMM6903I
Response to Prepare Flash request.
FMM6904I
Response to Restore request.
FMM6905I
Response to Flash request.
FMM6906I
Response to Verify request.
FMM6907I
Response to Complete Restore request.
FMM6908I
Response to Expiration request.
FMM6909I
Response to Monitor request.
FMM6910E
Could not set user ID to userid. Error error - errormsg.
FMM6911E
The effective user ID userideff of the process could not be set to the user userid. Error error - error_msg. Check that the device agent executable has the s-bit set.
FMM6912E
Background operation shutting down in order to give precedence to a concurrent operation.
FMM6913E
Wrong parameter provided with option '-c'.
FMM6914E
Invalid option '-K' specified.
FMM6915E
Could not change directory to path.
FMM6916E
Program program, function function: received signal signal, exiting.
FMM6917E
Failed to find volume group for file: path
FMM6918E
Error when reading the correlation list or during the FlashCopy of the volume pairs.
FMM6919E
Failed to cancel the copy relationship of volume pairs: rc=return_code.
FMM6920E
After 'withdraw done' was finished the update of the IDS repository failed: rc=return_code.
FMM6921E
Failed to monitor the FlashCopy.
FMM6922E
Failed to allocate memory.
FMM6923I
Object_name control object already initialized.
FMM6924E
Failed to initialize object_name control object.
FMM6925E
Function call 'function_name' failed.
FMM6926I
Adding 'path' to the Disk Mapper input list.
FMM6927E
Failed to find N-Series volume for file 'path'. Error: error_information.
FMM6928E
File system not found. Failed to find NFS mount point for file: 'path'.
FMM6929E
Not a file system of type NFS. Failed to find N-Series volume for file: 'file'.
FMM6930E
Volume information missing. Failed to find N-Series volume for file: 'path'.
FMM6931E
Function call 'function_name' failed. Error: error_information.
FMM6932E
Function call 'function_name' failed with rc_return_code. Error: error_information.
FMM6933I
Volume 'volume_id', snap ID _ snapshot_id.
FMM6934I
The snapshot 'snapid' was generated for the source volume 'volname'.
FMM6935I
Unmounting 'mount_point'.
FMM6936E
Failed to unmount 'mount_point'.
FMM6937I
Mounting 'mount_point'.
FMM6938E
Failed to mount 'mount_point'.
FMM6939I
Prepare for snap restore, volume 'volume_id', snap ID _ snapshot_id.
FMM6940I
Prepare flash of group 'group_id'.
FMM6941I
<server name><user name><separator><hw nas nseries><timeout>
FMM6942E
The storage device 'number' is not handled by this device agent.
FMM6943I
Hardware version installed: version.information
FMM6944I
NLS and tracing are already initialized.
FMM6945I
File system 'PATH' was already unmounted.
FMM6946E
The environment variable 'ODMDIR' is not specified. Verify that the DB2 registry parameter DB2ENVLIST contains the value 'ODMDIR'. To set the DB2ENVLIST you need to issue the command: db2set -i <DB2 instance name> DB2ENVLIST='<current envlist> ODMDIR'
FMM6947W
File system 'mount_point' is already mounted.
FMM6948E
The container 'container' has already been created. Please specify another name.
FMM6949E
Creation of the container 'container' failed because no preceding group has been found, or the preceding group is not valid. Current group is: 'group'. First specify a valid group using the 'command' command.
FMM6950W
The output file 'path' is not valid.
FMM6951E
Version mismatch error. Please check setup (version:information).
FMM6952E
Error in connection to IBM Tivoli Storage FlashCopy(R) Manager management agent.
FMM6953E
Error while parsing path script. The keyword 'keyword' is not supported during function_name.
FMM6954E
Error while parsing script. The keyword 'keyword' is not supported.
FMM6955E
'container_id' is not a valid container. Please specify a valid container.
FMM6956E
The usability state 'usability_state' is not supported.
FMM6957E
Script has continued without waiting.
FMM6958I
Output from script:
FMM6959I
Script 'path' returned with code return_code.
FMM6960E
Non-zero return code from script 'path'.
FMM6961E
Specify a script for removing data.
FMM6962I
Response to File System Service request (request).
FMM6963I
Performing snapshot of the source volume 'source volume'.
FMM6964I
Number of volumes to be processed by snapshot: 'number'.
FMM6965I
Snapshot started ...
FMM6966I
Snapshot successful.
FMM6967E
The directory directory has nested mount points that are stored on more than one volume group. This is currently not supported.
FMM6968E
'command_1' is not a valid keyword, expected 'command_2'.
FMM6969E
Found non-database files on the file systems to restore. Please provide a negative list or perform restore with option 'no_check' to allow overwriting those files.
FMM6970I
Snapshot restore successful.
FMM6971E
Adding the key 'key' to the container 'container' failed because it already exists. Please use the 'command' command if you want to update the key.
FMM6972E
Updating the key 'key' in the container 'container' failed because it does not exist. Please use the 'command' command if you want to add the key.
FMM6973E
The group 'group' has already been created. Please specify another name.
FMM6974E
'group' is not a valid group. Please specify a valid group.
FMM6975E
Adding the key 'key' to the group 'group' failed because it already exists. Please use the 'command' command if you want to update the key.
FMM6976E
Updating the key 'key' in the group 'group' failed because it does not exist. Please use the 'command' command if you want to add the key.
FMM6977E
The #'first_command' 'parameter' command has to be preceeded by a #'second_command' command.
FMM6978E
'command' is not a valid keyword when updates to containers and groups are expected.
FMM6979E
Script has continued without waiting. Expected output 'command' from script but was: 'output'.
FMM6980W
Received a warning from the adapter:warning
FMM6981E
Received an error from the adapter:error
FMM6982W
The script 'adapter_name' returned with code 1. The logfile might contain further warnings.
FMM6983E
The following backup items were not assigned to corresponding snapshot items:backup_items
FMM6984E
Error during prepare phase. Nothing known about group 'group_name'. It has not been created in the partition phase.
FMM6985E
Unable to connect to the copy services servers 'server name' and 'backup server name'.
FMM6986E
No matching target LUNs could be found in the selected target set for the source volumes 'volume list' .
FMM6988I
Executed command: 'command'
FMM7048I
The default port to connect to server_name will be used.
FMM7049I
The default for environment variable PROLE_PORT will be used.
FMM7050E
The 'datastore name' datastore has not been found in the datacenters defined in the domain. It is not part of the backup.
FMM7051E
The environment variable XINT_PROFILE is not set. It must be set and contain the fully qualified path to the *.utl file to be used.
FMM7052E
Only one line of effective input is allowed in the input file 'input filename' for the requested operation.
FMM7053E
Service setup failed due to previous error.
FMM7054I
The datastore pattern 'datastore pattern' will be expanded within the defined domain.
FMM7055E
Service open failed due to previous error in data mover.
FMM7056E
Service open failed because configured TSM server could not be accessed.
FMM7057E
Service open failed because all configured sessions are currently in use.
FMM7058E
Service open failed because more than one file was found with the same name.
FMM7059E
Service open failed because the file was not found.
FMM7060I
Data Protection for SAP(R) version.release.modification.level (build build_number)beta build_date session: process id
FMM7061I
Continuing to restore from next data copy.
FMM7062E
To create number_copies redo log copies at least number_sessions sessions and number_mgmtclasses different BRARCHIVE management classes are required. But currently only configured_sessions sessions are available.
FMM7063W
The profile parameter BACKUPIDPREFIX is no longer valid for Data Protection for SAP HANA(R) and will be ignored.
FMM7064W
Seems the previous operation was not completed successfully. Cleaning up.
FMM7065W
The executable 'executable_name' was called using the obsolete function specification 'obsolete_function'. You must use the updated function specification '-f function' instead.
FMM7066E
Determining the size of the application failed with the following error:message
FMM7301W
Data exchange file from Data Protection for Snapshot Devices for SAP(R), filename does not exist.
FMM7302W
The 'vm template name' virtual machine template with the 'vm instance uuid' instance UUID is ignored and is not part of the backup since it is a template.
FMM7303W
Profiles for Data Protection for Snapshot Devices for SAP(R) are different. backup: file name backup restore: file name restore
FMM7304I
Performing DISK ONLY backup.
FMM7305E
Error during call to Data Protection for Snapshot Devices for SAP(R): error message
FMM7307W
Data Protection for Snapshot Devices for SAP(R) reported an error during a snapshot-type operation.Do you want to continue backing up to TSM?
FMM7308E
DISK ONLY backup has failed.
FMM7309W
Data Protection for Snapshot Devices for SAP(R) reported an error during a snapshot-type operation. Do you want to continue restoring from TSM?
FMM7310W
Data Protection for Snapshot Devices for SAP(R) reported an error during a snapshot-type operation. CAUTION: Not all filesystems are available. Do you want to retry the operation?
FMM7311I
Profile used by Data Protection for Snapshot Devices for SAP(R): profile name.
FMM7312W
Profile for Data Protection for Snapshot Devices for SAP(R) not specified in profile. For restore this must be specified.
FMM7313W
Inquire results from Data Protection for Snapshot Devices for SAP(R) are not available.
FMM7314E
The data you want to restore is not available on the TSM server.
FMM7315W
The copy process for the files you want to restore is not finished. If you continue the operation, the files will be restored from the TSM server.
FMM7316I
The following backup types for the BACKUPID backup id have been found: - TSM - Snapshot
FMM7318E
The Data Protection for Snapshot Devices for SAP(R) profile file name is not valid.
FMM7319I
Start TSM restore.
FMM7320I
Start restore from snapshot.
FMM7321E
The Data Protection for Snapshot Devices for SAP(R) profile file name found in parameter FCS_FILE of the Data Protection for Snapshot Devices for SAP(R)(R) profile can not be used if you need to restore this backup.
FMM7322E
Request for a partial restore or restore from snapshot with "brrestore -m all" is not supported. In case of brrestore attempt rerun with -m full.
FMM7323W
Request for a partial restore or restore from snapshot with "brrestore -m all" is not supported. If you want to restore the backup: - with FlashCopy restore enter stop and rerun brrestore with "-m full" - from TSM enter cont
FMM7324E
Restore of multiple backup ID's in one run from a snapshot is not possible.
FMM7325E
Redirected restore from a snapshot is not possible.
FMM7535W
Error while executing command. Reason: errno(error number) explanation
FMM7536I
Execute command 'command name':
FMM7540E
None of the INCREMENTAL_LEVEL parameters specified in the profile can be used for the current operation.
FMM7541E
The environment variable ORACLE_SID must be set.
FMM7542I
A level number incremental backup using Oracle RMAN has started.
FMM7543I
Recreate database control file 'file_name'.
FMM7544E
The copy of the database control file 'file_name' was not found.
FMM7545I
Please enter the password for the user 'user_name' to connect against the recovery catalog database 'catalog_database_identifier':
FMM7546E
Failed to verify the password. This is the output of the failed command:
FMM7547E
Failed to verify the password. This is the output of the failed command:
FMM7548E
Incremental backups require IBM Tivoli Storage FlashCopy(R) Manager V3.1 or higher.
FMM7549E
Database 'identifier' is still running on host 'host_name'.
FMM7550E
Operation was cancelled by Oracle RMAN. Please check the log for more details.
FMM7551E
Failed to determine the database ID:
FMM7552E
Failed to determine the SCN:
FMM7553I
Restoring files from backup with ID backup_ID using Oracle RMAN ...
FMM7554E
The password to connect against the recovery catalog database 'identifier' is not set.
FMM7555E
Files from different RMAN backups can not be restored within a single operation.
FMM7556E
Restore of RMAN backups to a different location is not supported.
FMM8201E
SIMULATION CANCELED BY PRODUCTION OPERATION!!!
FMM8202E
There are no target sets specified in the volumes file that can be used with device section and parameter 'value'.
FMM8203E
There are no volume sets specified in the volumes file that can be used with 'device class' and STORAGE_SYSTEM_ID set to 'hardware id'.
FMM8204E
All volume sets that are specified in the volumes file identified in 'device class' require that the parameter STORAGE_SYSTEM_ID also be specified in the device section of the profile.
FMM8205E
There are no target sets specified in the volumes file that can be used with device section .
FMM8206W
The parameter profile parameter refers to the device class section(s) 'device class' which do not exist currently in the profile. Currently existing device class sections are: 'existing device class' If you proceed the missing device class sections are added to the profile automatically. If this is not intended, you must modify the specified device class names.
FMM8207E
Directory target dir does already exist. To perform IBM Tivoli Storage FlashCopy(R) Manager tape backup this directory must not exist. After deleting this directory run an unmount and perform the tape backup again.
FMM8268E
The database resides on 'database_volume_mgr' volumes but the profile specifies 'profile_volume_mgr' as the volume manager.
FMM8270W
The data mover 'keyword' is already defined in the profile.
FMM8271W
The given auxiliary host name 'keyword' cannot be resolved.
FMM8272W
Failed to set the VE_DATAMOVER_AUXHOST default auxiliary ESX host 'keyword' because a default already exists.
FMM8300I
Function_name returned with code return_codereturn_information.
FMM8301E
Product_name: Exception caught in function function_name. Error information: 'error_information'
FMM8302E
Product_name: Exception caught in function function_name. More information may be available in file log_file_name. Error information: 'error_information'
FMM8303E
No segment_name section found for the instance 'id'.
FMM8304W
The following error occured while verifying the configuration for section 'section':
FMM8305E
Invalid option option in options string: 'options_string'.
FMM8306E
The keyword keyword is not allowed multiple times within the profile.
FMM8307E
The parameter keyword must be specified in the profile.
FMM8308E
Single argument required for parameter keyword.
FMM8309E
Missing argument for parameter keyword.
FMM8310E
The keyword keyword is not allowed.
FMM8311E
For parameter keywortd, both server and port must be specified.
FMM8312E
Error while parsing parameter keyword. In order for 'value1' to be valid 'value2' is required to be an existing directory.
FMM8313E
Product_name: interface problem in function function_name: Invalid value of parameter: value
FMM8314E
Product_name: interface problem in function function_name: The session is already in use by a different operation.
FMM8315E
Function_name: The following object is not under the control of product_name: path
FMM8316E
Product_name: interface problem in function function_name: Empty group list passed by DB2.
FMM8317W
Product_name: Verification of configuration requested by user. No backup started.
FMM8318E
Product_name: interface problem in function function_name: Not enough space provided to write meta data.
FMM8319W
Error while deleting old versions.This problem does not affect the new backup.Error information: 'error_information'
FMM8320I
Deleting full backup backup_id - backup_key.
FMM8321I
Deleting partial backup backup_id for node host:partition_number.
FMM8322E
Interface problem: Current database partition number is not listed in the partition list.
FMM8323E
Product_name: Problem occurred while processing function_name. Please check log file log_file_name for more information. Error information: 'error_information'
FMM8324E
Product_name: Problem occurred while processing function_name: Device agent returned code return_information.
FMM8325E
Failed to determine hostname.
FMM8326E
Failed to create log directory path.
FMM8327E
Invalid value specified for parameter keyword: value
FMM8328E
Product_name must be licensed to set parameter keyword to a value of value.
FMM8330E
Parameter keyword requires 'YES', 'NO', or AUTO.
FMM8331E
The parameter keyword1 is not allowed if keyword2 is set to value.
FMM8332E
Failed to parse parameter keyword. File and path names in the profile need to be fully qualified.
FMM8333E
In order to enable the parameter keyword1 you need to set keyword2 to value.
FMM8334E
Profile section section_name is required for function operation.
FMM8335E
Profile section section_name refers to a value for keyword that differs from the one used at backup time. Expected value: value.
FMM8336E
Invalid value specified for option keyword: value
FMM8337E
Error while parsing profile: Missing section name.
FMM8338E
Error while parsing profile: Section section_name is not allowed to be nested.
FMM8339E
Error while parsing profile: Profile section section_name is not valid.
FMM8340E
Error while parsing profile: Profile section section_name must not be specified more than once.
FMM8341E
Error while parsing profile: Profile section section_name missing.
FMM8343W
The profile parameter keyword profile parameter of device type provile section has changed its value from (original)value1 to (current) value2.
FMM8344E
Path path is listed more than once for partitioning.
FMM8345E
Error while parsing parameter keyword. 'path' is required to be type_information.
FMM8349I
Deleting incomplete backup backup_id - backup_key.
FMM8350E
Parameter parameter requires "NO", "TSM", or "DP4SAP".
FMM8351E
Parameter parameter requires 'AUTO' or a decimal value.
FMM8352E
Parameter parameter requires a decimal value.
FMM8353E
Parameter parameter requires a value greater than '0'.
FMM8354E
Parameter parameter requires 'NO' or 'YES'.
FMM8355E
Parameter parameter requires 'ALL' or a comma separated list of decimal values.
FMM8356E
product_name: interface problem in function function: Invalid call sequence; the library was not initialized.
FMM8357E
product_name: interface problem in function function: Invalid call sequence; the operation was not initialized.
FMM8358E
Parameter name requires 'ONLINE' or 'OFFLINE'.
FMM8359E
The profile parameter parameter has the wrong value 'value profile'. The expected value is 'value expected'.
FMM8360E
Invalid keyword specified in the profile.
FMM8361E
Found files on the file systems to backup for which backup was not explicitly requested. Please provide a negative list or clean your file systems.
FMM8362E
The trace parameters YES, NO, ON, and OFF cannot be set in conjunction with other trace parameters.
FMM8363E
The value value is not a valid trace flag.
FMM8364E
Error while parsing parameter CONFIG_FILE. Directory 'directory' for node 'node' does not exist.
FMM8365E
The server stanza for LOG_SERVER 'server' is missing.
FMM8366E
The values for parameter parameter are expected to be in the range 0 to 6.
FMM8367E
You cannot freeze the filesystem without suspending or shutting down the database.
FMM8368E
An invalid argument is specified for keyword keyword.
FMM8369E
Failed to execute program. Reason: reason.
FMM8370E
The profile option TARGET_DATABASE_SUSPEND = OFFLINE is not allowed for an online database backup.
FMM8371E
The profile parameter NEGATIVE_LIST is not allowed. Use BR-TOOLS option "-n" to specify the negative list.
FMM8372E
The profile option TARGET_DATABASE_SUSPEND=YES requires a backup of type volume_online. To solve this problem either the profile parameter TARGET_DATABASE_SUSPEND can be set to OFFLINE or NO or the brbackup backup device type should be set to util_vol_online. Keep in mind, when you set the profile parameter TARGET_DATABASE_SUSPEND to NO, the snapshot backup will be mounted on a backup system to verify its consistency. Make sure that a backup system is configured in that case.
FMM8373W
The operation will execute the force option (-F).
FMM8374W
Operation will terminiate with error, because backint was executed with verify option (-V).
FMM8375E
The value of the environment variable ORACLE_SID is not allowed to have more than number digits.
FMM8376E
Verification of snapshot failed. Reason:reason
FMM8377E
Function function does not support multiple backup ids within a single operation.
FMM8378E
Redirected restore of volume backups is not supported yet.
FMM8379E
Infile contains an invalid value: 'value'
FMM8380E
The profile option TSM_BACKUP=YES requires a snapshot backup of all partitions of the database.
FMM8381W
The following error occured while verifying the configuration for server 'server_name' in the profile:
FMM8382E
The previous error(s) can be prevented by executing restore with negative list set to "no_check".
FMM8383E
BR-Tools are required to set the environment variable BI_RUN for volume backups.
FMM8384E
Failed to determine the APPLICATION_TYPE of the profile. Please invoke wizard with option -m <application type>.
FMM8385E
In order to create a new profile the wizard needs to be invoked with option -m <application type>.
FMM8386E
Parameter parameter name requires a decimal value of 0 or greater.
FMM8387W
The following extra files are found in the directories to be backed up: 'filename'
FMM8388W
Additional files to restore were discovered on the file systems: 'file list'
FMM8389W
The following volume groups / file systems are currently not accessible: volumegroups/filesystems
FMM8390E
Failed to validate that only database files will be overwritten during restore, because some of the database filesystems are currently not accessible. Please import volume groups and/or mount all filesystems and restart the restore. If you cannot mount the filesystems as a consequence of a disaster or a failing previous restore operation, this error can be prevented by executing restore with negative list set to "no_check".
FMM8391E
'bytes_requested' bytes were requested to be read from the file 'filename' but only 'bytes_read' bytes could be read.
FMM8392E
An error occured while restoring the file 'filename'
FMM8393E
The keyword TARGET_SET requires a target set name as argument.
FMM8394E
Error while parsing TARGET_SET target set name: Illegal number of arguments.
FMM8395E
Error while parsing TARGET_SET target set name in volumes file: A multi partition backup requires the use of the keyword PARTITION in the target set section.
FMM8396E
Error while parsing TARGET_SET target set name in volumes file: It is not allowed to specify a portion of a target set without keyword PARTITION, if this keyword is used for other portitions in the same target set definition.
FMM8397E
Error while parsing TARGET_SET target set name in volumes file: the parameter PARTITION requires exactly one parameter.
FMM8398E
Error while parsing statement 'parameter name' in profile. The statement 'from or to' is required to be in the form hh:mm.
FMM8399E
The mode mode of parameter parameter is only supported for device_type .
FMM8400E
Error while parsing statement 'device class' in profile. The statement partition number is required to be a number.
FMM8401E
DEVICE_CLASS device class was encountered multiple times within a single DEVICE_CLASS statement.
FMM8402E
No DEVICE_CLASS found that can be used for the current operation.
FMM8403E
The keyword keyword was found multiple times without qualifier qualifier.
FMM8404E
The following statement contains incompatible options statement.
FMM8405E
The following statement is missing mandatory options statement.
FMM8406E
There are two object type associated with partition partition name.
FMM8407E
An illegal partition number has been specified for parameter candidate name.
FMM8408E
The parameter parameter is not allowed as a name for a target set.
FMM8409E
The parameter TARGET_NAMING is required to contain the wildcards source and targetset.
FMM8410I
Invoking suspend script suspend script.
FMM8411I
Script returned with return code return code
FMM8412I
Start resume script resume script.
FMM8413I
Continue script script to resume.
FMM8414E
Error while parsing profile profile: Delimiter 'delimiter' missing.
FMM8415E
A size has been specified for the file 'file' in the infile, but the requested file is not a raw device.
FMM8416E
The specified backup ID 'backup id' must have 16 characters.
FMM8417E
File 'file' has not been found in any backup.
FMM8418E
The backup ID 'backup id' has not been found.
FMM8419E
File 'file' was not found in the backup identified with backup ID 'backup id'
FMM8420E
Full file-based backups into the repository are not allowed when 'ALLOW_FULL_FILE_BACKUP' is set to 'NO'.
FMM8421I
Modifying existing profile 'profile file' for application 'application type' ...
FMM8422I
Creating new profile 'profile file' for application 'application type' ...
FMM8424E
Operation not allowed for this parameter.
FMM8426I
Saving profile 'profile' ...
FMM8428W
No help available for this parameter
FMM8431E
Application Type 'application type' is not a valid type.
FMM8432E
Invalid function: function invalid (supported: function supported)
FMM8433E
Wrong system mode: system mode (supported: PS | BS | PSBS)
FMM8435W
Annotation file 'file' could not be loaded.
FMM8436W
Problems occured on final validation of profile. Incorrect parameters have been marked in the written profile. Please check.
FMM8437I
Verifying password...
FMM8439E
Could not read password filename from profile 'profile'. File does not exist. (Check options -p, -b)
FMM8440E
'number of disks' disks have been found for datastore 'datastore name'. Only one disk per datastore is supported for the following environments: IBM DS8000 IBM NSeries NetApp.
FMM8441E
Please specify either only backup id's or only backup id's with files.
FMM8445E
Invalid cloning mode: cloning mode invalid (supported: cloning_only | backup_cloning)
FMM8446E
The restore operation requires the command line option -P <Partition group> to be specified.
FMM8448E
Another device class already exists under the given name 'name'. Please specify another name.
FMM8450E
The entry in InFile is not a valid file or directory: 'entry'.
FMM8463W
The 'file' file does not exist. It must be created before the configuration can be used by IBM Tivoli Storage FlashCopy(R) Manager.
FMM8464W
The specified host name or IP address 'host' cannot be associated with a local network interface on this system.
FMM8465E
The value value for parameter parameter is out of valid range (min - max).
FMM8467E
"-d" flag is deprecated for Oracle environments. The source database name is determined automatically.
FMM8468W
The front-end capacity report for total protected size for this database is not available. Front-end capacity will be set to 0.
FMM8503E
No ESX host that can be used for instant restore was found.
FMM8504E
The 'datastore name' data store cannot be mounted on the following ESX hosts: 'ESX host list'. There are no other ESX hosts to try.
FMM8505E
The 'data store name' data store is mounted on the following disconnected ESX hosts: 'ESX host list'. The data store cannot be unmounted when these ESX hosts are in the disconnected state.
FMM8506E
The configured storage device cannot be used in a VMware NAS environments.
FMM8507W
The original data store cluster cannot be found: 'datastore cluster name'. The data store 'datastore name' is restored to the root directory of data center 'data center name'.
FMM8508E
An invalid value was specified for parameter parameter name in the IBM Tivoli Storage FlashCopy(R) Manager profile. The following options must not be specified: list of invalid options.
FMM8509E
The directory 'directory' or one of its parent directories could not be created on the backup system or the IBM Tivoli Storage FlashCopy(R) Manager instance owner user does not have write permission to the directory. The specified directory is required for a temporary control file copy. Create the directory on the backup system and ensure that the IBM Tivoli Storage FlashCopy(R) Manager instance owner user has write permissions to it.
FMM8510E
Database instance 'instance name' could not be started because the default database profile could not be found.
FMM8511I
The command is: command name
FMM8512I
Return code is: return code
FMM8513W
'TDP_DIR' is not set. The temporary path will be used.
FMM8514W
'TDP_DIR' is not set correctly. The temporary path will be used.
FMM8515W
Volume volume group is shared across partitions. This might result in severe restrictions during the restore operation. Consult the manual for details.
FMM8516E
The restore operation terminated because more objects than requested would have been restored.
FMM8517E
Function 'name' cannot operate on multiple partitions simultaneously. Run the operation again with a single partition.
FMM8518E
Unable to stop db2.
FMM8519E
Unsupported database / application type.
FMM8520E
No command was specified.
FMM8521E
Command option 'command option' requires an argument.
FMM8522E
Invalid command 'command'.
FMM8523E
Error during action.
FMM8524E
An online restore of the Tablespace is not allowed.
FMM8525E
The DB2 instance name can consist of at most characters characters.
FMM8526E
The DB2 database alias can consist of at most characters characters.
FMM8527E
Invalid node. Specify it in the format node format.
FMM8528E
Invalid timestamp. Specify the format as 'yyyymmddhhmmss', wildcards '*' or '?' are permitted.
FMM8529E
Invalid log sequence number. Specify it in the format log sequence format.
FMM8530E
Profile 'file name' does not exist or cannot be accessed.
FMM8531E
Directory 'file path' does not exist or cannot be accessed.
FMM8532E
Invalid log chain number. Specify it in the format log chain format.
FMM8533E
A timestamp range is not allowed for command 'command'.
FMM8534E
Command option 'command option' is missing.
FMM8535E
Invalid output mode. Specify one of the keywords keyword list.
FMM8536E
Wildcard characters are not allowed for command 'command'.
FMM8537E
The path 'path' is not absolute.
FMM8538E
The Tablespace Definition Information 'file name' cannot be processed.
FMM8539E
The parameter PARTITION_GROUP is not allowed in the client section for non-SAP environments. The DB2_WORKLOAD parameter must specify SAP.
FMM8540I
Using component_name at host name:port
FMM8541I
Using profile 'profile path'.
FMM8542E
Profile 'profile path' cannot be read.
FMM8543I
Querying TSM for file(s) 'file list'.
FMM8544I
Application agent is terminating.
FMM8545I
No image typeimage(s) found.
FMM8546E
Environment variable 'environment variable' is not set or not set correctly.
FMM8547E
Nothing to restore.
FMM8548I
Elapsed time: time value
FMM8549E
Unable to create file 'file name'.
FMM8550W
Environment variable 'environment variable' for output mode has wrong value. Using default.
FMM8551E
Not all data written to 'file path'.
FMM8552E
File 'file path' could not be closed.
FMM8553E
The file 'filename' has not been found. This file is required for the device agent to function. Check your installation.
FMM8554E
Unable to create directory for detailed logs: name of directory.
FMM8555E
Variable "DB2DBDFT" or command option "alias" is required.
FMM8556E
Unable to get hostname.
FMM8557E
The config file "initfile name.bki" could not be created.
FMM8558I
Setting TSM password for partition 'partition number' on host 'host name'.
FMM8559W
For partition 'partition number' switch to host 'host name' and issue the command again.
FMM8560E
Partition 'partition number' not found in the database configuration.
FMM8561W
Database 'alias' not listed in the system database directory.
FMM8562E
Target 'volume' is missing in the target set ('target set name') that has been specified for restore. Review the error explanation for corrective actions.
FMM8563E
The target name 'backup volume' could not be identified from source name 'source volume' and target set 'target set' using the current naming convention. Please review the error explanation for corrective actions.
FMM8564E
The backup selected for restore resides on target set 'name'. Either this target set definition no longer exists in the profile or the manner in which the target sets were specified has changed. Please consult the user manual for corrective actions.
FMM8565E
More than one DEVICE_CLASS statement is eligible for the current operation. This is not allowed.
FMM8566E
The specified DEVICE_CLASS statements are inconsistent. As a result, these pairs are ambiguous: pairs
FMM8567E
A node configured in PARTITION_GROUP is not present in the db2nodes.cfg file or does not reside on this host. To restore nodes that reside on a different host you need to start the restore from this host directly.
FMM8568I
All nodes from db2nodes.cfg will be restored.
FMM8569I
Only some nodes specified in the db2nodes.cfg file will be restoredAdditional restore operations might be required on other hosts.
FMM8570E
Unable to start db2.
FMM8571E
Unable to initialize db2.
FMM8572I
Output of db2inidb: output.
FMM8573I
The password file 'filename' has been updated successfully.
FMM8574E
Syntax error: syntaxerror
FMM8575E
In this command multiple passwords were set for 'server'. Only one password can be set for each server.
FMM8576E
The profile section 'sectionname' does not need a password.
BKI8577E
The 'directory' file does not exist which is mandatory for the correct operation of the related storage device adapter.
FMM8578E
The backup operation cannot be run because the RMAN backup script 'file name' does not contain the keyword "backup" on a single line of text.
FMM8583E
Multiple possible values for parameter 'INCREMENTAL_LEVEL' detected:ambigous statements
FMM8584I
Delete command completed successfully.
FMM8585W
Delete command completed successfully, but had warning(s).
FMM8586I
Delete command was aborted.
FMM8587E
Delete command failed due to an error.
FMM8588E
Delete command has not been started or no delete result information is available.
FMM8589E
Query command failed due to an error.
FMM8596E
The virtual machine 'vm name' with instance UUID 'source vm instance uuid' cannot be backed up because it is distributed across multiple datastores. Distributed virtual machines are not supported for the following environments: IBM DS8000 IBM NSeries NetApp.
FMM8601E
The following device class sections are missing in the profile:
FMM8602E
The parameter profile parameter is referring to device class section 'device class' which does not exist in the profile.
FMM8603E
Parameter illegal option is not a valid parameter for keyword profile parameter.
FMM8610I
Restoring type ...
FMM8611I
Do you want to overwrite the existing database (y/n)?
FMM8612I
Continuing restore ...
FMM8613E
Terminating restore ...
FMM8614E
The virtual machines 'vm1' and 'vm2' have the same UUID 'uuid'. UUID's need to be unique within a backup run.
FMM8615I
Restore command completed successfully.
FMM8616W
Restore command completed successfully with warnings.
FMM8617I
Restore command was aborted.
FMM8618E
Restore command failed due to an error.
FMM8619E
Restore command has not been started or no restore result information is available.
FMM8621I
Restoring file 'file name' ...
FMM8622I
Deleting type ...
FMM8623I
Deleting file 'file name' ...
FMM8626W
The Tablespace Definition Information 'file name' could not be deleted.
FMM8628E
Found VM with name 'vmname' in datastore 'dsurl' but not in the backup or in the infile.
FMM8629E
The 'variable name' environment variable is not set.
FMM8630E
The command option 'option' must be a number.
FMM8631I
Backup command completed successfully.
FMM8632W
Backup command completed successfully with warnings.
FMM8633E
The configured vCenter(TM) server is the 'found API version' version, which is not supported by IBM Tivoli Storage FlashCopy(R) Manager.
FMM8634E
Backup command failed due to an error.
FMM8635E
The command option 'option' must be a floating point number.
FMM8636E
The command option 'option' must be one of values.
FMM8637I
Type state backup of 'alias' started ...
FMM8638I
Type state backup of tablespace(s) tablespace#1,...,tablespace#n of 'alias' started ...
FMM8639I
Including log files in backup image ...
FMM8640I
Using number buffers with a size of size ...
FMM8641I
Using number session(s) ...
FMM8642I
Using a degree of parallelism of number ...
FMM8643I
Using vendor library at 'lib path' ...
FMM8644W
Offline backups cannot include log files. The option -L is being ignored.
FMM8648I
number of files in this run file(s) were stored successfully in this run on the 'hostname' node. A total number of stored number of files totally files out of total number of files files are stored in the data backup that is identified by the external 'backup id' backup ID.
FMM8649E
The automatic deletion of backups is not supported. Change the value of the parameter name parameter to 0.
FMM8650E
To restore from all found_copies detected redo log copies, required_sessions sessions must be opened. But currently only configured_sessions are allowed.
FMM8651W
Your version of DB2 does not support including log files. The option -L is being ignored.
FMM8652I
DB2 version 'version' with number bits detected.
FMM8653I
Using autonomic buffer size and number of buffers ...
FMM8654I
Using an autonomic buffer size with number buffers ...
FMM8655I
Using an autonomic number of buffers with a size of size ...
FMM8656I
Using an autonomic degree of parallelism ...
FMM8657W
Number is not a valid partition number for a non-partitioned database. Assuming partition 0.
FMM8658E
Number is not a partition number of the database or does not denote a partition on this host.
FMM8659I
Creating tablespace definition information ...
FMM8660I
Saving tablespace definition information ...
FMM8661W
Could not create Tablespace Definition Information.
FMM8662W
Could not save Tablespace Definition Information.
FMM8663W
The Tablespace Definition Information contains device containers of a type unsupported by BackOM redirected restore.
FMM8664E
Connecting to 'alias' using CLI failed. The return code was return code.
FMM8665I
The backup timestamp is: timestamp
FMM8666I
Redirecting container of tablespace table space with ID id.
FMM8667W
Tablespace tablespace with ID id was not redirected because its container on source system SID is not located in a path starting with 'path'.
FMM8668I
Tablespace Definition Information created successfully.
FMM8669I
Free space of device with ID id containing the container storage path 'storage_path' are free_space.
FMM8670I
Remaining free space of device with ID 'id' after assigning container 'container_name' of size size are free_space.
FMM8671I
Using automatic storage path(s) storage_path.
FMM8672I
Redefining container path(s) of automatic storage tablespace tablespace with ID id.
FMM8673E
The Datastore name 'dsname' is not unique within one Backup.
FMM8674E
A syntax error was detected in the filename file: token
FMM8675E
The default value for the parameter_name parameter in the filename file is missing.
FMM8676E
The 'datastore name' datastore already exists on the datacenter.
FMM8681E
One of the target datastores is not available on the ESX host. The datastore cannot be found by using the original URL 'datastoreurle' or any other URL.
FMM8682W
The current user ID does not have permissions to create or update tasks in the vCenter.
FMM8690E
Free space check for container 'path' failed. Only free bytes free space left on device with ID 'id' but required bytes required.
FMM8691E
The password file 'file name' cannot be read.
FMM8692E
The requested data could not be retrieved.
FMM8693E
More than one Tablespace Definition Information file matches your query.
FMM8700E
Internal parser error in Tablespace Definition Information parser.
FMM8701E
This parser cannot process Tablespace Definition Information version version.
FMM8702E
Too many errors. Bailing out.
FMM8703E
Out of memory.
FMM8704E
Error while reading input file.
FMM8705E
Error in line line number.
FMM8706E
The container at 'path' is inappropriate for tablespace tablespace.
FMM8707E
Missing statement keyword in block block name near line line number.
FMM8708E
The [TDI] header block must be the first block.
FMM8709E
The required block block name is missing.
FMM8710W
Duplicate block block name ignored at line line number.
FMM8711W
Duplicate statement keyword ignored in line line number.
FMM8715E
Failed to create directory 'path'. Reason: reason
FMM8727E
No instance found managing database 'database name'.
FMM8728E
Could not attach to instance 'instance'.
FMM8729I
Checking system resources ...
FMM8730I
Scaling tablespace containers to number percent ...
FMM8731I
Normalizing tablespace containers ...
FMM8732E
The Tablespace Definition Information used with the redirected restore operation contains an invalid database alias.
FMM8733E
The Tablespace Definition Information used with the redirected restore operation contains an invalid instance name.
FMM8734E
The Tablespace Definition Information used with the redirected restore operation contains an invalid partition number.
FMM8735E
The input file 'input file name' is not allowed to be empty.
FMM8736E
Tablespace tablespace must have at least one container.
FMM8737E
Tablespace tablespace has containers with the combined storage too small.
FMM8738E
The container at path has a page size that is incompatible with its tablespace.
FMM8739E
The type of the container at path is incompatible with its tablespace.
FMM8740E
The path path of a container must not be relative.
FMM8741E
The container at path would overwrite existing files or directories.
FMM8742E
The container at path is a device container which is not supported.
FMM8743I
Local Tablespace Definition Information check returned return code.
FMM8744I
Tablespace Definition Information replacement check returned return code.
FMM8745E
The Tablespace Definition Information is invalid.
FMM8746I
The Tablespace Definition Information is valid.
FMM8747E
Not all tablespaces of the original database are contained in the Tablespace Definition Information.
FMM8748E
The Tablespace Definition Information does not define enough storage to hold all the data of the original database.
FMM8749E
The page size of a tablespace in the Tablespace Definition Information does not match the one of the original database.
FMM8750E
The number of used pages of a tablespace in the Tablespace Definition Information does not match the one of the original database.
FMM8751E
The tablespace type in the Tablespace Definition Information does not match the one of the original database.
FMM8752E
BackOM does not support redirected restore with device containers.
FMM8753E
A container cannot be created at path.
FMM8755I
Getting reference Tablespace Definition Information from TSM ...
FMM8756W
Could not get reference Tablespace Definition Information from TSM. No input validation is done.
FMM8757I
Performing redirected restore from 'source alias' to 'target alias' ...
FMM8758E
The Tablespace Definition Information does not contain data for tablespace 'tablespace'.
FMM8759E
Redirecting of at least one container failed.
FMM8760E
Directory 'directory' could not be created.
FMM8761E
The container at path does not have the minimum size of two extends.
FMM8762I
Set tablespace container with ID id and name 'tablespace_container'.
FMM8763E
The extent size of a tablespace in the Tablespace Definition Information does not match the one of the original database.
FMM8765I
Checking redirected restore from 'source alias' to 'target alias' ...
FMM8766I
Check successful. Redirected restore possible with these settings.
FMM8767W
Warnings occurred.
FMM8768E
Check failed. Redirected restore not possible with these settings.
FMM8769E
Found multiple Tablespace Definition Information matching the given timestamp. Additional search conditions needed.
FMM8770I
Getting Tablespace Definition Information used with the redirected restore operation from TSM...
FMM8771E
The Tablespace Definition Information used with the redirected restore operation could not be retrieved.
FMM8772E
The selected database has a structure that prevents automatic cloning.
FMM8773E
The interactive modification of the containers failed.
FMM8776E
You are not allowed to delete this container.
FMM8798E
Due to errors, you cannot continue the operation.
FMM8799E
A container must have a size of at least twice the extent size (minimum size for this tablespace).
FMM8800I
The command is: command
FMM8801I
Time: time --- PID: PID_Number
FMM8802I
Found number type image(s) on TSM server.
FMM8803I
The DB2 image size for this session is about 'size'.
FMM8804W
The recovery log could not be written.
FMM8805I
The restore was cancelled by the user. Existing data not overwritten.
FMM8806I
product version.release.modification.level (build_numberbeta) build_date
FMM8807I
Archive log file 'log number' of chain 'log chain number'.
FMM8808I
Retrieve log file 'log number' of chain 'log chain number'. Seeking for TSM image 'image'.
FMM8809W
Disk group 'disk group name' could not be mounted on one or more of the following remote Oracle RAC nodes: 'node name list'.
FMM8810I
Cleaning up resources of process 'PID_number'.
FMM8811E
The shutdown of database 'db name' was not successful on the following database nodes: 'node names'.
FMM8812I
Committed TSM sessions of this backup run will be deleted.
FMM8813E
Error deleting committed TSM sessions.
FMM8814I
Inquired TSM with mask 'search mask'.
FMM8815I
Information for Log Manager: DB2_instance DB2_database_name DB2_database_alias log_and_log_chain_number partition
FMM8816I
DB2 version 'version' detected.
FMM8817I
No corresponding committed TSM session(s) found. Nothing will be deleted.
FMM8818W
Invalid value specified for BACKOM_LOCATION.
FMM8819I
The TSM objects matching with mask 'search mask' will be deleted.
FMM8820E
No valid TSM session found.
FMM8821I
Using option(s) 'options'.
FMM8822I
Configuration parameter(s):parameters
FMM8823W
Configuration parameter SRC_DB_ALIAS requires parameter SRC_DB_INSTANCE and vice versa.
FMM8824I
Partitioning backup image into segments of maximum 'size'.
FMM8825I
Creating commit object for session session_id comprising overall number segment(s).
FMM8826I
Found database image 'image_name' partitioned into number segment(s).
FMM8827E
Missing commit object.
FMM8828E
A backup object segment associated with backup image 'image_name' is missing.
FMM8831E
The properties of the virtual machine 'vm name' could not be fetched through the vSphere API because they are not set.
FMM8832I
Note: The GSKit installation is not removed from ${HOSTNAME} because it might be in use by other IBM Tivoli Storage FlashCopy(R) Manager instances. If needed, the GSKit can be manually uninstalled. For more information, see the Installation and User's Guide.
FMM8833W
The environment variable 'SHLIB_PATH' does not include the path '/usr/lib' which is required for the correct operation of GSKit. Ensure that the path is added to allow the correct operation of IBM Tivoli Storage FlashCopy(R) Manager.
FMM8834E
An earlier version of GSKit is running: 'version'. This version cannot be used for Transport Layer Security (TLS) version 1.2.;
FMM8835I
Starting synchronous reconcile operation.
FMM8836I
The reconcile operation has finished.
FMM8837I
The synchronous reconcile operation has terminated. Normal processing continues.
FMM8838I
Starting synchronous delete operation.
FMM8839I
The delete operation has finished.
FMM8840I
The synchronous delete operation has terminated. Normal processing continues.
FMM8841W
No IBM Tivoli Storage FlashCopy(R) Manager offload daemon was running in the last minutes minutes. Make sure that the IBM Tivoli Storage FlashCopy(R) Manageroffload daemon process is running.
FMM8842W
The 'lunserial' Logical Unit Number (LUN) was added to the 'dsName' datastore after the backup was completed. This LUN will be detached from the vSphere environment.
FMM8843E
The virtual machine could not be restored using 'target vm name' VM name. A VM with the same name already exists in the datacenter.
FMM8899E
Interface problem in function function: Value 'value' of parameter 'parameter' is not supported with DB2 version 'version'.
FMM9001E
Internal error: error
FMM9002E
Parameter 'all' is not supported.
FMM9003E
Incompatible components installed: component name one, component name two
FMM9004E
Location of the message catalog could not be figured out.
FMM9005E
A not supported by B
FMM9006E
Internal error while reading environment variable: variable
FMM9007W
An error occurred while terminating the application:the error
FMM9008E
This product requires at least version number of product name to be installed.
FMM9009W
The following products are not compatible: product name first (product version first) and product name second (product version second).
FMM9010E
Could not determine installation directory for program. Please restart the process using a fully qualified name.
FMM9011E
There was no response received within number seconds; timeout is expired. You can increase the timeout by specifying the profile parameter timeoutphase for the current phase of the backup or restore operation.
FMM9012E
One of the requested data containers is already the subject of a restore.
FMM9013E
Concurrent restore of objects being backed up with multiple device agents is not supported.
FMM9014E
Failed to load library: library reason: reason
FMM9015E
Failed to locate functions in library: library reason: reason
FMM9016E
The database is not mounted.
FMM9017E
The file system 'mountpoint' on volume group 'volume group' contains data and redo log files from the same database instance.
FMM9018E
The volume group 'volume group' contains file systems with data files, and file systems with redo log files.
FMM9019E
The following control files are not included in any database or redo log file volume groups: List of Controlfiles
FMM9020E
The following database File Type files are on the root volume group: List of Files
FMM9021E
Querying the operation system information for the following files and file systems failed: List of Files
FMM9022I
Volume group layout check (fcm.volume_group_layout): In Network File System (NFS) environments, this check validates if the prerequisites for database filesystems layout are fulfilled. In Oracle Automatic Storage Management (ASM) environments, this check validates if the prerequisites for the database disk groups layout are fullfilled. In all other environments, this check validates if the prerequisites for the database volume groups layout are fulfilled. The respective requirements are listed in the Pre-installation Checklist PDF that is published in the Requirements Technote.
FMM9023E
The volume group 'volume group' contains database files as well as the file or folder 'volume group':
FMM9024E
The following control files are included in a data file volume group: List of Controlfiles
FMM9025I
The database version check (fcm.db_Version) validates if the database level is supported by IBM Tivoli Storage FlashCopy(R) Manager. If a newer database version is found, verify if it is supported by referring to the Requirements Technote.
FMM9026I
The application check (fcm.application_environment) validates if the application is DB2 or Oracle DB.
FMM9027I
The storage management network connection check (storage.validatePort) validates if storage management can be reached through the TCP/IP network.
FMM9028E
The file system 'volume group' contains database files and the file or folder 'volume group':
FMM9029E
The file system 'mountpoint' contains both data and redo log files from the same database instance.
FMM9030E
The following database File Type files are on the root file system: List of Files
FMM9031E
The file system 'volume group' contains both data files and redo log files.
FMM9032E
The following control files are included in the file system where the database data files are stored: List of Controlfiles
FMM9033E
The following control files are not included in a file system for database or redo log files: List of Controlfiles
FMM9035I
The current profile does not specify preprocessing or postprocessing scripts. For consistent (blank)application backups, you must specify these scripts at the command-line when you enter (blank)a backup command. Alternatively, edit the profile in advanced mode (-advanced option) to specify the scripts.
FMM9036E
The file system File System is not of expected type File System Type
FMM9037E
The following volume group(s) contain an unsupported mix of file system types: Volume Groups
FMM9038E
The file system File System in volume group Volume Group does not belong to the database.
FMM9039W
As no database environment was found for user User, the Application Type is set to Custom Application (CAA). The volume group layout (fcm.volume_group_layout) and file system type checks (fcm.fileSystemType) cannot be run.
FMM9040I
Starting check for property 'property'
FMM9041I
Completing check for property 'property'
FMM9042W
The volume group layout (fcm.volume_group_layout) and file system type checks (fcm.fileSystemType) cannot be run because the database is on Oracle ASM disk groups.
FMM9043W
The volume group layout (fcm.volume_group_layout) and file system type checks (fcm.fileSystemType) cannot be run because the database is a DB2 PureScale database.
FMM9044W
The volume group layout (fcm.volume_group_layout) and file system type checks (fcm.fileSystemType) cannot be run because the database is a DB2 DPF (Database Partitioning Feature) database.
FMM9045I
The volume group layout support check (fcm.is_vg_layoutcheck_supported) validates if the volume group layout (fcm.volume_group_layout) and file system type checks (fcm.fileSystemType) can be run on the database.
FMM9046I
The file system type check (fcm.fileSystemType) validates if the files to be managed by IBM Tivoli Storage FlashCopy(R) Manager are in supported filesystems.
FMM9047W
Log message(s) for partition Partition Number, loggend on host Host Name: Log Message(s)
FMM9048E
Log message(s) for partition Partition Number, loggend on host Host Name: Log Message(s)
FMM9049I
End of log message(s) for partition Partition Number on host Host Name.
FMM9050E
There is not sufficient free space available in path Path. Make sure the free space amounts to at least Number of Available Bytes bytes.
FMM9051W
No data files were found for partition Partition Number of database Database Name.
FMM9052W
No database log files were found for partition Partition Number of database Database Name.
FMM9053W
No data files were found for database Database Name.
FMM9054W
No database log files were found for database Database Name.
FMM9055I
Log message(s) for host Host Name: Log Message(s)
FMM9056W
Log message(s) for host Host Name: Log Message(s)
FMM9057E
Log message(s) for host Host Name: Log Message(s)
FMM9058I
End of log message(s) for host Host Name.
FMM9059E
Querying the operation system information for the following files and file systems failed on host Host Name for the follwing files: List of Files
FMM9060E
The file system File System on host Host Name is not of expected type File System Type.
FMM9061E
The following database File Type files are on the root volume group of host Host Name: List of Files
FMM9062E
The following database File Type files are on the root file system of host Host Name: List of Files
FMM9063E
On host 'Host Name', the file system 'Mountpoint' on volume group 'Volume Group' contains data and log files of the same database.
FMM9064E
On host 'Host Name', the file system 'mountpoint' contains both data and log files of the same database.
FMM9065E
On host 'Host Name', the volume group 'Volume Group' contains file systems with data files and file systems with log files of database 'Volume Group'.
FMM9066E
On host 'Host Name', the file system 'Mountpoint' contains both data files and log files of database 'Volume Group'.
FMM9067E
The volume group 'Volume Group' on host 'Host Name' contains database files as well as the file or folder 'File Name'.
FMM9068E
The file system 'Mountpoint' on host 'Host Name' contains database files and the file or folder 'File Name'.
FMM9069E
Volume group 'Volume Group' on host 'Host Name' contains File Type files of partition 'Partition Number 1' and of partition 'Partition Number 2'.
FMM9070W
Volume group 'Volume Group' on host 'Host Name' contains File Type files of partition 'Partition Number 1' and of partition 'Partition Number 2'. These partitions must always be backed up and restored together.
FMM9071E
No database was found in instance 'Instance Name' owned by 'Instance Owner'.
FMM9072I
Log message(s) for partition Partition Number, loggend on host Host Name: Log Message(s)
FMM9073E
The file system File System in volume group Volume Group of host Volume Group does not belong to database Database Name.
FMM9074I
In DB2 DPF environments, the check for shared volumes (fcm.no_shared_volumes) checks whether a volume group contains database files of two or more partitions.
FMM9075I
The check of volume layout for cloning (fcm.volumes_for_cloning) validates that there is at least one control file located in a volume group or filesystem where database redo logs reside.
FMM9076W
No control file of database 'Database Name' was found in a volume group where database redo logs were also located.
FMM9077W
No control file of database 'Database Name' was found in a filesystem where database redo logs are also located.
FMM9078W
The current configuration applies both device types 'SVC' and 'SVCDTA' to the same IBM Storwize v7000 / IBM System Storage SAN Volume Controller server. If you save these settings, the following restrictions will apply: 1) no new backups can be created for DEVICE_CLASS sections of type 'SVC' 2) existing backups that were created with DEVICE_CLASS of type SVC can be attached and restored on a file-copy basis only (individual VM or disk restore) 3) you cannot restore these backups by using an instant restore (flashback of an entire datastore)
FMM9079E
File 'File Name' on host 'Host' is not a data file or a log file of database 'Database Name'.
FMM9080E
Database 'Database Name' is not an active database.
FMM9081E
The parameter parameter_name must not be set to 'ADAPTIVE' in combination with DEVICE_CLASS sections configured for the IBM Storwize v7000 / IBM System Storage SAN Volume Controller that use dynamic target allocation (device type 'SVCDTA')
FMM9082I
You configured this DEVICE_CLASS section for IBM Storwize v7000 / IBM System Storage SAN Volume Controller using dynamic target allocation (device type 'SVCDTA'). Note that in this case the parameter MAX_VERSIONS of the VMWARE profile section must not be set to ADAPTIVE. Ensure that you set the parameter MAX_VERSIONS to a fixed limit.
FMM9083E
The current configuration applies both device types "SVC" and "SVCDTA" to the same IBM Storwize v7000 / IBM System Storage SAN Volume Controller server. This setup requires that those DEVICE_CLASSes of type "SVC" are configured in a downgraded mode so that only mount operations are allowed. The profile is missing the necessary tags.
FMM9084I
In DB2 DPF environments, the check for shared volumes (fcm.warn_no_shared_volumes) checks whether a volume group contains database files of two or more partitions.
FMM9085E
A TCP/IP connection could not be established to port 'Port' at host 'Host'. Reason: 'Reason'
FMM9086E
The backup function is not allowed for a DEVICE_CLASS using the device type SVC when another DEVICE_CLASS is using the same storage server and the device type SVCDTA.
FMM9087E
The instant restore function is not allowed for a DEVICE_CLASS using the device type SVC when another DEVICE_CLASS is using the same storage server and the device type SVCDTA.
FMM9088E
The SSH connection could not be established because the file permissions of the 'ssh key file' SSH private key file are too open.
FMM9089W
The SSH connection could not be established. The following error message was generated by the SSH command: 'ssh error'
FMM9090W
The SSH port 22 on the 'svc name' SVC storage system could not be connected. Check the SSH port on the storage system.
FMM9091E
The 'data store name' data store is mounted on the following disconnected ESX hosts: 'ESX host list'. The operation cannot be performed when these ESX hosts are in the disconnected state.
FMM9092W
The current configuration applies both device types 'SVC' and 'SVCDTA' to the same IBM Storwize v7000 / IBM System Storage SAN Volume Controller server. If you save these settings, the following restrictions will apply: 1) no new backups can be created for DEVICE_CLASS sections of type 'SVC' 2) existing backups that were created with DEVICE_CLASS of type SVC can be attached and restored, but will result in the destruction of newer backups, even if they were created using the new adapter.
FMM9093I
You configured this DEVICE_CLASS section for IBM Storwize v7000 / IBM System Storage SAN Volume Controller using dynamic target allocation (device type 'SVCDTA'). Note that the parameter MAX_VERSIONS in the CLIENT profile section or the parameter MAX_SNAPSHOT_VERSIONS in the .utl file must not be set to ADAPTIVE. Ensure that you set this parameter to a fixed limit.
FMM9094I
Command mmbackup was run successfully: mmbackup_output
FMM9095E
Command mmbackup failed:
FMM9096I
Offloading of backup with ID backup ID to IBM Tivoli Storage Manager server(s) server list ended successfully on timestamp.
FMM9198E
While processing path path_name, an error occurred. The following error information was received: detailed_error_information
FMM9199E
The following command returned with an error: command The return code from this command is return_code The following command output was received: command_output Additional support information: An exception was thrown at position: position(line).
FMM9200E
Additional support information: An exception was thrown at position: position(line).
FMM9201E
Additional support information: An exception was thrown at position: position(line).
FMM9202E
Additional support information: An exception was thrown at position: position(line).
FMM9203E
Additional support information: An exception was thrown at position: position(line).
FMM9204E
Additional support information: An exception was thrown at position: file(line) (text_description).
FMM9205E
Additional support information: Unable to instantiate name at file(line).
FMM9206E
Additional support information: Unable to use actual when expecting expected at file(line).
FMM9207E
Additional support information: An exception was thrown at position: file(line).
FMM9208E
System error errno: errno text at position: file(line).
FMM9209E
Additional support information: No handler registered for message type message. Thrown at position: file(line).
FMM9210E
ESD_AbortDispatchingException thrown at position: file(line).
FMM9211E
Additional support information: An exception was thrown at position: file(line). (State state)
FMM9212E
Additional support information: No handler registered for message type (message_type, classname). Thrown at position: file(line).
FMM9213E
A memory allocation request failed at position: file(line).
FMM9214E
Additional support information: An exception was thrown from a destructor.
FMM9215E
The maximum string length supported for name is length.
FMM9216E
Additional support information: An exception was thrown at position: file(line).
FMM9217E
Additional support information: An exception was thrown at position: file(line).
FMM9218E
Additional support information: An exception was thrown at position: file(line).
FMM9219E
Additional support information: Invalid error type type encountered.
FMM9220E
Additional support information: Second call of call.
FMM9221E
The operation ended prematurely with return code rc. An exception was thrown at position: file(line).
FMM9222E
A snapshot-type operation was interrupted, Additional support information: An exception was thrown at position: file(line).
FMM9223E
The operation will be aborted.
FMM9224E
The operation will be aborted. Check for other error messages in the log files.
FMM9225E
The keyword 'keyword' has not been found in the line 'line' of the file 'file_name'. Please change it back to the original value if you modified it.
FMM9226E
The ASM instance with SID='instance id' is not available. Please check if the ASM_INSTANCE_ID is set to the right ASM instance, if yes start it and check the availability.
FMM9227E
The ASM diskgroup 'diskgroup' has not been found. Ensure that it is available.
FMM9228E
Excpected ASM file but found file: 'file'
FMM9229E
Excpected file but found ASM file: 'file'
FMM9230E
The SSL/TLS certificate provided by the server is missing a valid subject DN or issuer DN field.
FMM9231E
The SSL/TLS certificate provided by the server is not proving its supposed identity.
FMM9300E
Additional support information: Aborting 'send' operation. See previous error.
FMM9301E
Additional support information: State state does not match state pattern pattern.
FMM9302E
Additional support information: A process ended unexpectedly. Check previous error messages.
FMM9306I
Dumping callstack.
FMM9307E
Did not find a winsock dll compatible with version major_winsock version.minor_winsock version. Version found is low_byte_available version.high_byte_available version.
FMM9308E
A socket request timed out after processing number of bytes bytes. file(line).
FMM9309E
Operation terminated due to an explicit abort request.
FMM9310E
Could not add backup_id to the repository at path.
FMM9311E
Could not find backup_id in the repository at path.
FMM9312E
backup_id is currently locked in the repository at repository.
FMM9313E
Failed to update backup_id in the repository at path.
FMM9314E
Could not remove backup_id from the repository at path.
FMM9315E
Could not access the repository at 'path' because it is currently locked by another process.
FMM9316E
The name 'name' refers to an existing file or directory, but it does not appear to be a valid repository. In order to continue you need to specify either a non existing directory or the path of an existing valid repository.
FMM9317E
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.
FMM9318E
The file 'filename' has not been found. It is required for the device agent to function. Check your installation.
FMM9319E
Operation is terminated.
FMM9320W
Warning: Backup of previous profile version failed (file access error).
FMM9327I
Note: No IBM Tivoli Storage FlashCopy(R) Manager server certificate found in key database and no self-signed certificate file "${GSK_SELFSIGN_CERT}" found to be imported. If not using CA signed certificates, import self-signed certificate from Production System (PS). For details, refer to the User"s Guide.
FMM9328E
An error occurred in the secure communication layer when running the following function: function. GSKit return code: numeric return code. GSKit error: return value.
FMM9329E
An error occurred when the software tried to link the SSL Implementation to GSKit. GSKitWrapper error: 'linker error'
FMM9330E
Error: Invalid Server name. The server name must be longer than min but cannot exceed max characters. The current length is len.
FMM9331E
Error: Invalid User name. The user name must be longer than min but cannot exceed max characters. The current length is len.
FMM9332E
Error: Invalid User password. Run 'fcmcli -f password' to create the password. The password must be longer than min but cannot exceed max characters. The current length is len.
FMM9333E
Error: Invalid Secondary Server name. The server name cannot exceed a length of max characters. The current length is len.
FMM9334E
Error: Invalid Server installation directory. The path to install directory cannot exceed a length of max characters. The current length is len.
FMM9335E
Error: Invalid Java home directory. The path to the Java Home directory cannot exceed a length of max characters. The current length is len.
FMM9336E
Error: Invalid Port number. The port number cannot be higher than max. The current port is port.
FMM9337W
The given port number port is already in use by another process.
FMM9339E
The specified device class name is already in use by section section.
FMM9340E
The FlashCopy Cloning operation failed because the FlashCopy mappings used for Cloning are dependent on older FlashCopy mappings from older FlashCopy Backup or Cloning operations. You can either wait until the older FlashCopy mappings are in state idle_or_copy or you can start the Cloning operation with the force option [-F] which will force the older FlashCopy mappings to be stopped. In the latter case you will loose your older FlashCopy Backups or Clones.
FMM9341E
The name of the clone database is missing.
FMM9342E
Unmounting of file system 'filesystem' at backup system does not work.;