This chapter describes the messages issued by Tivoli Data Protection for IBM ESS for R/3. The messages begin with the prefix IDS and are listed in numerical order.
IDS1000E | Profile not specified |
Explanation: TDP for ESS 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>....
IDS1001E | Function not defined |
Explanation: An invalid argument has been specified for the -f option of TDP for ESS.
User Response: Ensure that you pass a valid function name with the option -f. Valid functions are: withdraw, flashcopy, password, unmount, and inquire.
IDS1004E | Subfunction not defined. |
Explanation: An invalid argument has been specified for the -s option of TDP for ESS. 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.
IDS1005I | Start of idscntl program at: time. |
Explanation: TDP for ESS started at time.
User Response: None.
IDS1007I | End of idscntl program at: time. |
Explanation: TDP for ESS 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.
IDS1008E | Parameter <keyword> in the profile file required. |
Explanation: The parameter <keyword> in the profile for TDP for ESS could not be found. It must be defined.
User Response: Set the parameter <keyword> and its value in the profile for TDP for ESS.
IDS1009E | 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.
IDS1010E | Option -i <backup_list> not specified. |
Explanation: The function -f flashcopy requires the specification of the option -i <backup_list> too.
User Response: Ensure that you transfer the list of the files to back up when you call the function -f flashcopy. Note that the idscntl call must in this case have the following form: <path>/idscntl -p <path>/init<SID>.fcs -f flashcopy -i <backup_list> ... When the FlashCopy 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.
IDS1011E | 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>....
IDS1014I | <subsystem message> |
Explanation: TDP for ESS received an information message from the IDS subsystem.
User Response: None.
IDS1015W | <subsystem message> |
Explanation: TDP for ESS received a warning message from the IDS subsystem.
User Response: None.
IDS1016E | <subsystem message> |
Explanation: TDP for ESS received an error message from its IDS control part.
User Response: See the subsystem error messages for more information and perform required action.
IDS1024I | 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.
IDS1025I | Time stamp: <current_time> |
Explanation: TDP for ESS performs several tasks in sequence (e.g. initiate the FlashCopy of source volumes on the production system and mount file systems on the backup system). Tracking the various time stamps allows analyzing how long each task took.
User Response: None.
IDS1026I | Start of idscntl on the production system ... |
Explanation: TDP for ESS has issued a call to the production system and is waiting for the end of the execution.
User Response: None.
IDS1027I | idscntl ended on the production system successfully. |
Explanation: TDP for ESS has ended the call to the production system successfully.
User Response: None.
IDS1030I | Flashcopy started ... |
Explanation: The command with the flashcopy function has been issued on the production system, and the program idscntl waits until this action has finished.
User Response: None.
IDS1031I | Flashcopy successful. |
Explanation: The command for the FlashCopy of the volume pairs has terminated successfully on the production system.
User Response: None.
IDS1032W | Information from TDP for R/3 was not found. |
Explanation: The exchange data between TDP for ESS and TDP for R/3 was not found during the execution of the unmount function. Either the TDP for R/3 you have installed does not support TDP for ESS, or TDP for R/3 has failed after a successful FlashCopy and mount.
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 disk (FlashCopy target volumes) as well as the one done to the TSM server are valid. However, TDP for ESS cannot show the BACKUPID in its report when using the function inquire.
Reason for warning: It is very likely that TDP for R/3 (AIX version) does not have TDP for ESS support (prior to version 3.1.0.3).
Action: Install the appropriate TDP for R/3 version.
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 disk (FlashCopy target volumes) 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.
IDS1033I | Information from TDP for R/3 has been found with BACKUPID <backupid>. |
Explanation: The exchange data between TDP for R/3 and TDP for ESS has been found during the execution of the function unmount. The backup on disk (FlashCopy target volumes) as well as to the TSM server are valid. The list of files has been saved in the Tivoli Storage Manager with the BackupID <backupid>.
User Response: None.
IDS1034E | Entry <field_name> in the current backup cycle of the IDS control file is missing. |
Explanation: The field with the name <field_name> in the current backup cycle was unexpectedly empty.
User Response: Please check for other errors prior to this one.
IDS1035I | The IDS control file exists and a new backup cycle entry has been created. |
Explanation: At the start of the function -f flashcopy, TDP for ESS 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. FlashCopy target volumes/filesystems being mounted or unmounted).
User Response: None.
IDS1038I | The IDS control file <ids_control_file> does not exist. It will be created. |
Explanation: TDP for ESS will write the first record to the IDS control file specified in the entry IDS_CONTROL_FILE of the profile.
User Response: None.
IDS1039E | The IDS control file has no entry. |
Explanation: TDP for ESS has found the IDS control file, but it has no records. This error occurs when you start one of the functions inquire, withdraw or unmount before you have run the flashcopy function for the first time.
User Response: After you run at least one brbackup with a successful flashcopy, the problem will be resolved.
IDS1040E | The IDS control file must be read or inserted before update. |
Explanation: TDP for ESS has detected a logical error when processing the IDS control file.
User Response: Contact Tivoli Data Protection for R/3 support.
IDS1043I | 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.
IDS1044I | 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.
IDS1045W | 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.
IDS1046I | Start of listing of importing volume groups/mounting file systems ... |
Explanation: After initiating the FlashCopy source/target volumes on the production system, TDP for ESS will make the corresponding target volumes available to the backup host. A list of mount points or volume groups will be shown.
User Response: None.
IDS1047I | End of listing. |
Explanation: Corresponds to start message IDS1046I.
User Response: None.
IDS1048E | The progress status indicator cannot be PSI_MOUNT_DONE when you call the flashcopy function. |
Explanation: TDP for ESS 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 FlashCopy operation is requested.
User Response: Run the unmount function and try again.
IDS1050E | The version of the idscntl program must be the same on the backup and production systems. |
Explanation: The version of TDP for ESS 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 ESS on the production and backup systems. You get the version number when you start idscntl without parameters.
IDS1051I | 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 ESS 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.
IDS1052I | 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.
IDS1053I | 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.
IDS1054E | 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 flashcopy function is used.
IDS1055E | The config file named <config_file> could not be opened. Please call idscntl with the password function to create that file. |
Explanation: TDP for ESS is unable to read the configuration file <config_file>.
User Response: This error could have various reasons. Try the following:
1. Call idscntl with the 'password' function to create the file.
2. Check the path of the configuration file. The path must be specified in the profile (parameter CONFIG_FILE).
3. Make sure that the file access permissions are set correctly.
IDS1060I | Start of listing of exporting volume groups/unmounting file systems ... |
Explanation: A list of unmount points or exporting disk groups will be shown. Due to the usage of the unmount function on the backup host,TDP for ESS will unmount the file systems and export volume groups on the backup host that had been imported or mounted when the TDP for ESS flashcopy function was executed.
User Response: None.
IDS1061I | Start the withdraw of the target-source pairs ... |
Explanation: The command with a withdraw has been issued from the backup system to the primary Copy Services server on the ESS.
User Response: None.
IDS1062I | The progress status indicator (PSI) is already PSI_UNMOUNT_DONE. |
Explanation: TDP for ESS has been called with the function withdraw 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.
IDS1063E | Parameters LOGON_HOST_PROD/LOGON_HOST_BACK in profile wrong or missing. |
Explanation: Either TDP for ESS 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.
IDS1064E | 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.
IDS1065W | The progress status indicator (PSI) is already PSI_WITHDRAW. |
Explanation: You cannot run the flashcopy unmount function multiple times without having done a brbackup with a flashcopy request. Doing this will cause warnings. It might be that a previous flashcopy request failed due to network problems and the unmount could therefore not be done.
User Response: Make sure you run a brbackup with the function -f flashcopy prior to using the TDP for ESS unmount function.
IDS1066E | The option -f flashcopy can only be used on the backup system. |
Explanation: You cannot start the flashcopy function on the production system.
User Response: Make sure you start idscntl with the function -f flashcopy on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK.
IDS1067E | The options -f flashcopy -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 issue idscntl -f flashcopy 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.
IDS1068E | The option -f withdraw can only be used on the backup system. |
Explanation: You cannot start the function withdraw on the production system.
User Response: Make sure you start idscntl with the function -f withdraw on the backup system only. Ensure that the profile contains a valid entry for LOGON_HOST_BACK.
IDS1069E | 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.
IDS1071E | Topic named <topicname> could not be found in the file <filename>. |
Explanation: TDP for ESS could read the file <filename> but the expected entry for the topic <topicname> was not found.
User Response: When the affected file is the field value of the parameter SHARK_VOLUMES_FILE, you need to check whether the topic name has the format: >>> shark_volumes_set_# where # is a placeholder for the volume set number (1, 2, ..)
When the affected file is another file, you likely have another error prior this one. Otherwise, contact Tivoli Data Protection for R/3 support.
IDS1072E | The progress status indicator must be PSI_WITHDRAW when you call the function flashcopy. |
Explanation: TDP for ESS has found that the progress status indicator of the latest backup cycle still has a value of PSI_UNMOUNT_DONE. This indicates that, although the file systems are already unmounted, the withdraw function was not yet called. This check will be done only if the parameter FLASCHCOPY_TYPE is set to NOCOPY.
User Response: Run the withdraw function and try again.
IDS1073E | No target volumes were specified for the set <shark_volumes_set_#> in file <filename>. |
Explanation: TDP for ESS has read file <filename> contained in the parameter SHARK_VOLUMES_FILE. The format of the file is correct, but the list of target volumes is missing.
User Response: See a description of the FlashCopy target volumes file.
IDS1075I | Creating a semaphore for the critical part of importing ... |
Explanation: When multiple production systems run a backup via a single backup system at the same time, TDP for ESS will ensure that the critical part of the code, which is the phase when the FlashCopy has been done and resources (volume groups and file systems) are being enabled, runs for a single instance of the program at a time. For this synchronization process, a semaphore with the fixed key 0x88886666 will be created.
User Response: None
IDS1076I | Trying to set the semaphore for the critical part of importing ... |
Explanation: If the TDP for ESS semaphore is already allocated, the program will wait until it is released. Otherwise, the program will set it and pass into the critical part of the run. Another instance arriving at this point will now have to wait for the release of the semaphore.
User Response: None
IDS1077I | Semaphore released. |
Explanation: After the program has passed the critical part of the run, the semaphore is released.
User Response: None
IDS1078W | The semaphore could not be created. System error <sys_errno>: <sys_message>. |
Explanation: If TDP for ESS could not create the semaphore, the system error number and message will be issued as a warning. The concurrent run of multiple production systems with a single backup system will not work properly.
User Response: Check the system error number and message with your system administrator.
IDS1079W | The semaphore could not be initialized. System error <sys_errno>: <sys_message>. |
Explanation: If TDP for ESS could not initialize the semaphore, the system error number and message will be issued as a warning. The concurrent run of multiple production systems with a single backup system will not work properly.
User Response: Check the system error number and message with your system administrator.
IDS1080W | The semaphore could not be allocated. System error <sys_errno>: <sys_message>. |
Explanation: If TDP for ESS could not allocate the semaphore, the system error number and message will be issued as a warning. The concurrent run of multiple production systems with a single backup system will not work properly.
User Response: Check the system error number and message with your system administrator.
IDS1081W | The semaphore could not be released. System error <sys_error>: <sys_message>. |
Explanation: If TDP for ESS could not allocate the semaphore, the system error number and message will be issued as a warning. The concurrent run of multiple production systems with a single backup system will not work properly.
User Response: Check the system error number and message with your system administrator.
IDS1300E | Cannot read file: <filename>. |
Explanation: TDP for ESS 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.
IDS1301E | Cannot write file: <filename>. |
Explanation: TDP for ESS 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.
IDS1302E | 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 ESS:
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.
IDS1303E | 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.
IDS1304E | File not found or not accessible: <filename>. |
Explanation: The file <filename> was not found or is not accessible to TDP for ESS. 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 back up).
User Response: Check path, name and the permissions of the file and try again.
IDS1305E | The effective user ID of the process could not be set to the user <userid>. |
Explanation: After installation, the command "ls -l idscntl" outputs a line such as:
-rwsr-x--- 1 root dba 1918611 Apr 11 17:09 idscntl
Since the s-bit is set, TDP for ESS can switch between the users 'root' and 'ora<sid>' during the execution of the program. The program is now unable to make that switch.
User Response: Ensure that the program has the permissions as shown above.