This chapter describes the messages issued by Tivoli Data Protection for EMC Symmetrix for R/3. The messages begin with the prefix IDS and are listed in numerical order.
IDS0000E | Profile not specified |
Explanation: TDP for Symmetrix cannot locate the profile.
User Response: Ensure that a profile is available. Note that the idscntl call must have the following form: <path>/idscntl -p <path>/init<SID>.fcs -f <function>....
IDS0001E | Function not defined |
Explanation: An invalid argument has been specified for the -f option of TDP for Symmetrix.
User Response: Ensure that you pass a valid function name with the option -f. Valid functions are: split, synchronize, unmount, password and inquire.
IDS0004E | Subfunction not defined. |
Explanation: An invalid argument has been specified for the -s option of TDP for Symmetrix. This option has been designed for internal idscntl use only and should not be used externally.
User Response: Do not use the -s option with the idscntl call.
IDS0005I | Start of idscntl program at: time. |
Explanation: TDP for Symmetrix started at time.
User Response: None.
IDS0007I | End of idscntl program at: time. |
Explanation: TDP for Symmetrix ended at time. Control will be returned to either the shell or to brbackup when idscntl was called by brbackup based on the entries split_cmd and resync_cmd in the brbackup profile (e.g., init<SID>.sap)
User Response: None.
IDS0008E | Parameter <keyword> in the profile file required. |
Explanation: The parameter <keyword> in the profile for TDP for Symmetrix could not be found. It must be defined.
User Response: Set the parameter <keyword> and its value in the profile for TDP for Symmetrix.
IDS0009E | Directory path <path> for the IDS control file does not exist. |
Explanation: Either the entry for the parameter IDS_CONTROL_FILE is incorrect or the path does not exist.
User Response: Ensure that the parameter IDS_CONTROL_FILE in the profile has a valid path. If the path does not exist, you must create it.
IDS0010E | Option -i <backup_list> not specified. |
Explanation: The function -f split requires the specification of the option -i <backup_list> too.
User Response: Ensure that you transfer the list of the files to backup when you call the function -f split. Note that the idscntl call must in this case have the following form: <path>/idscntl -p <path>/init<SID>.fcs -f split -i <backup_list> ... When the split function runs under the control of the R/3 DBA tool brbackup by means of the split_cmd statement of the R/3 DBA profile, you must ensure that the correct syntax is used there (e.g. "... -i $"). brbackup replaces the "$" character with the name of the list file.
IDS0011E | Option -f <function> not specified. |
Explanation: idscntl always requires the option -f <function> with a valid function.
User Response: Ensure that the idscntl call has the following form: <path>/idscntl -p <path>/init<SID>.fcs -f <function>....
IDS0014I | <subsystem message> |
Explanation: TDP for Symmetrix received an information message from the IDS subsystem.
User Response: None.
IDS0015W | <subsystem message> |
Explanation: TDP for Symmetrix received a warning message from the IDS subsystem.
User Response: None.
IDS0016E | <subsystem message> |
Explanation: TDP for Symmetrix received an error message from its IDS control part.
User Response: See the subsystem error messages for more information and perform required action.
IDS0024I | Exiting with return code <rc>. |
Explanation: The idscntl program issues this message on terminating. The program returns the value 0, or nonzero if the execution of the called function failed.
User Response: If the called function has failed, check for previous error messages.
IDS0025I | Time stamp: <current_time> |
Explanation: TDP for Symmetrix performs several tasks in sequence (e.g. split BCVs on the production system and mount file systems on the backup system). Tracking the various time stamps allows analysis of how long each task took.
User Response: None.
IDS0026I | Start of idscntl on the production system ... |
Explanation: TDP for Symmetrix has issued a call to the production system and is waiting for the end of the execution.
User Response: None.
IDS0027I | idscntl ended on the production system successfully. |
Explanation: TDP for Symmetrix has ended the call to the production system successfully.
User Response: None.
IDS0030I | Split started ... |
Explanation: The command for the split of the BCVs has been issued on the production system, and the program idscntl waits until this action has finished.
User Response: None.
IDS0031I | Split successful. |
Explanation: The command for the split of the BCVs has terminated successfully on the production system.
User Response: None.
IDS0032W | Information from TDP for R/3 was not found. |
Explanation: The exchange data between TDP for Symmetrix and TDP for R/3 was not found during the execution of one of the functions synchronize or unmount. Either the TDP for R/3 you have installed does not support TDP for Symmetrix, or TDP for R/3 has failed after splitting the BCV/STD pairs.
User Response: Check the run logs of brbackup. This error could have various reasons and should be resolved depending on the specific situation:
Case 1: brbackup has finished successfully.
Result: The backup on disks (BCVs) as well as the one done to the TSM server is valid. However, TDP for Symmetrix cannot show the BACKUPID in its report when using the function inquire.
Reason for warning: It is very likely that TDP for R/3 does not have TDP for Symmetrix support (prior to version 3.1.0.3).
Action: Install the appropriate TDP for R/3.
Case 2: brbackup has terminated abnormally.
Result: Check carefully the run log of brbackup for any BKI, ANS or ANR error messages. Most likely, the backup on disks (BCVs) is valid (check with 'idscntl -f inquire' whether PSI is PSI_MOUNT_DONE or PSI_UNMOUNT_DONE), but the backup to the TSM server is invalid.
Cause: Any problems with the network or on the TSM server caused TDP for R/3 running a backup to fail.
Action: Depending on the error message, eliminate the reason for not getting a successful backup to the TSM server.
IDS0033I | Information from TDP for R/3 has been found with BACKUPID <backupid>. |
Explanation: The exchange data between TDP for R/3 and TDP for Symmetrix has been found during the execution of one of the functions synchronize or unmount. The backup on disks (BCVs) as well as to the TSM server is valid. The list of files has been saved in the Tivoli Storage Manager with the BackupID <backupid>.
User Response: None.
IDS0035I | The IDS control file exists and a new backup cycle entry has been created. |
Explanation: At the start of the function -f split, TDP for Symmetrix inserts a record in the IDS control file for the new backup cycle. This record will be updated as the status of the new backup cycle changes (e.g. BCVs getting mounted, unmounted, synchronized).
User Response: None.
IDS0038I | The IDS control file <ids_control_file> does not exist. It will be created. |
Explanation: TDP for Symmetrix will write the first record to the IDS control file specified in the entry IDS_CONTROL_FILE of the profile.
User Response: None.
IDS0039E | The IDS control file has no entry. |
Explanation: TDP for Symmetrix has found the IDS control file, but it has no records. This error occurs when you start one of the functions inquire, synchronize or unmount before you have run the split function for the first time.
User Response: After you run at least one brbackup with a successful split, the problem will be resolved.
IDS0043I | The maximum number of backup cycles in the IDS control file has been reached. |
Explanation: The maximum number of backups controlled via the parameter BACKUP_MAX will be exceeded with the new inserted record. If the parameter is not set, the program will use the default value of 30.
User Response: None.
IDS0044I | Delete backup cycle with BSEQ_N = <bseq_n> and all associated files ... |
Explanation: Since the maximum number of records has been reached, the program will delete the oldest record with the backup sequence number <bseq_n>. In addition, the oldest reports and traces associated with that backup cycle will be deleted.
User Response: None.
IDS0045W | Directory path <directory> for the report files does not exist. Using the current directory. |
Explanation: The directory entry of the parameter LOG_TRACE_DIR in the profile could not be found. The current directory will be used for the log and trace files.
User Response: In order to avoid directories cluttered with reports and traces, the parameter LOG_TRACE_DIR should be used, or the directory it specifies must be created if necessary.
IDS0046I | Start of listing of importing disk groups/mounting file systems ... |
Explanation: After splitting the STD/BCV pairs on the production system, TDP for Symmetrix will make the corresponding target resources (BCVs) available to the backup host. A list of mount points or disk groups (VxVM) will be shown.
User Response: None.
IDS0047I | End of listing. |
Explanation: Corresponds to start message IDS0046I.
User Response: None.
IDS0048E | The progress status indicator cannot be PSI_MOUNT_DONE when you call the function split. |
Explanation: TDP for Symmetrix has found that the progress status indicator of the latest backup cycle already has a value of PSI_MOUNT_DONE. This indicates that the file systems are still mounted when a new STD/BCV split is requested.
User Response: Run the synchronize or unmount function and try again.
IDS0050E | The version of the idscntl program must be the same on the backup and production systems. |
Explanation: The version of TDP for Symmetrix on the production system is different from the version on the backup system.
User Response: Ensure that you install the same version of TDP for Symmetrix on the production and backup systems. You get the version number when you start idscntl without parameters.
IDS0051I | Enter the password for the user <user ID> |
Explanation: The password for the user ID <user ID> has to be entered. It will be encoded and stored in a file specified in the parameter CONFIG_FILE. Note that this user ID and password have to be the same on the production and backup systems. The TDP for Symmetrix program idscntl uses the user ID to execute a remote shell on the production system.
User Response: Enter the password for the corresponding user ID.
IDS0052I | Enter the password for the user <user ID> again |
Explanation: In order to avoid typing errors, you have to enter the password twice.
User Response: Enter the password again.
IDS0053I | The password entry does not match, please try again |
Explanation: The two entered passwords are not identical. You must enter the password again.
User Response: Enter the password again. You are permitted three attempts before the program terminates.
IDS0054E | No password stored. |
Explanation: The two entered passwords are not identical. You have tried three times, and the passwords were different in each case.
User Response: You must start the idscntl program with the function -f password again. If no password is stored, or it is invalid, idscntl fails when the split function is used.
IDS0055E | The config file named <config_file> could not be opened for reading/writing. |
Explanation: TDP for Symmetrix is unable to read the configuration file <config_file>.
User Response: This error could have various reasons. Try the following:
1. Check the path of the configuration file. The path must be specified in the profile (parameter CONFIG_FILE).
2. Make sure that the file access permissions are set correctly.
IDS0060I | Start of listing of deporting disk groups/unmounting file systems ... |
Explanation: Before synchronizing the STD/BCVs pairs, TDP for Symmetrix will disable the corresponding resources from the backup host. A list of unmount points or deporting disk groups (VxVM) will be shown.
User Response: None.
IDS0062I | The progress status indicator (PSI) is already PSI_UNMOUNT_DONE. |
Explanation: TDP for Symmetrix has been called with the function synchronize or unmount, but the PSI value of the latest backup cycle was already updated to PSI_UNMOUNT_DONE in a previous idscntl call.
User Response: None.
IDS0063E | Parameters LOGON_HOST_PROD/LOGON_HOST_BACK in profile wrong or missing. |
Explanation: Either TDP for Symmetrix is unable to read one of the parameters LOGON_HOST_PROD/LOGON_HOST_BACK from the profile, or the parameter values are incorrect. Note that these parameters must have the following format:
LOGON_HOST_PROD <hostname> <user ID>
LOGON_HOST_BACK <hostname>
The hostnames must match the respective hostnames of the production and backup systems. The user ID specified must match the oracle DBA user ID (ora<sid>).
User Response: Ensure that the profile contains valid entries for LOGON_HOST_PROD and LOGON_HOST_BACK.
IDS0064E | The parameter <keyword> in the profile is not known. |
Explanation: An unknown parameter <keyword> has been found in the profile.
User Response: Check the specified parameter in the profile and try again.
IDS0065W | The progress status indicator (PSI) is already PSI_SYNCHRONIZED. |
Explanation: You cannot run the synchronize/unmount function multiple times without having done a brbackup with a split request. Doing this will cause warnings. It might be that a previous split request failed due to network problems and the synchronization could therefore not be done.
User Response: Make sure you run a brbackup with the function -f split prior to using the TDP for Symmetrix functions unmount or synchronize.
IDS0066E | The option -f split can only be used on the backup system. |
Explanation: You cannot start the split function on the production system.
User Response: Make sure you start idscntl with the function -f split on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK.
IDS0067E | The options -f split -s performsplit can only be used on the production system. |
Explanation: The option -s was designed for internal idscntl use only and should not be used externally.
User Response: Make sure you start idscntl -f split on the backup system only. Ensure that the profile contains valid entries for LOGON_HOST_PROD and LOGON_HOST_BACK. Do not use the -s option with the idscntl call.
IDS0068E | The option -f synchronize can only be used on the backup system. |
Explanation: You cannot start the function synchronize on the production system.
User Response: Make sure you start idscntl with the function -f synchronize on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK.
IDS0069E | The option -f unmount can only be used on the backup system. |
Explanation: You cannot start the function unmount on the production system.
User Response: Make sure you start idscntl with the function -f unmount on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK.
IDS0070I | Checking and if necessary synchronizing STD/BCV pairs. |
Explanation: At this point, idscntl checks on the production system for the availability of synchronized STD/BCV pairs. If the pairs are not yet synchronized, idscntl will synchronize them at this point. However, this will take much more time than if the synchronization had been initiated on the backup system before running the brbackup that started a split request via the split_cmd statement.
User Response: Avoid this type of late synchronization in a brbackup run and synchronize the BCVs with the STDs before starting brbackup or within brbackup via the resync_cmd statement.
IDS0300E | Cannot read file: <filename>. |
Explanation: TDP for Symmetrix is unable to read the data file <filename>. The affected files could be e.g.: <ORACLE_HOME>/dbs/init<SID>.fcs, the argument value of the option -i (file containing the list of files to back up), <config_file>, <ids_control_file> or the field value of EXCHANGE_FILE in a backup cycle record.
User Response: Check the access permissions of the affected file and try again.
IDS0301E | Cannot write file: <filename>. |
Explanation: TDP for Symmetrix is unable to write to the data file filename. The
affected files could be e.g.:
<LOG_TRACE_DIR>/idscntl_b_<time>.log,
<LOG_TRACE_DIR>/idscntl_p_<time>.log,
<LOG_TRACE_DIR>/idscntl_b_<time>.trace,
<LOG_TRACE_DIR>/idscntl_p_<time>.trace,
<config_file>,
<ids_control_file> or
the field value EXCHANGE_FILE in a backup cycle record.
User Response: Check the access permissions of the affected file and try again.
IDS0302E | The environment variable <env_var> must be set. |
Explanation: The environment variable <env_var> is required. The following
environment variables must be set when running TDP for Symmetrix:
ORACLE_HOME: to the home directory of the user ID
ORACLE_SID: to the R/3 Oracle DB system ID
User Response: Set the missing environment variable and try again.
IDS0303E | The environment variable <env_var> is not correct. |
Explanation: This error can occur when the environment variable is set but contains a non-existent directory path.
User Response: Check the value of the environment variable and try again.
IDS0304E | File not found or not accessible: <filename>. |
Explanation: The file <filename> was not found or is not accessible to TDP for Symmetrix. The affected files could be: <ORACLE_HOME>/dbs/init<SID>.fcs or the argument value of the option -i (that file contains the list of files to backup).
User Response: Check path, name and the permissions of the file and try again.