CHAPTER 1. Enterprise Backup Utility Messages
EBU-100 Oracle7 Enterprise Backup Utility
None
EBU-101 String
None
EBU-102 String
None
EBU-103 Oracle7 Enterprise Backup Instance Manager
None
EBU-104 Started job job_ID with process_ID on hostname for database
None
EBU-106 Command script script_name, follows
None
EBU-108 DB_NAME = db_name
None
EBU-109 ORACLE_SID = sid
None
EBU-110 Error in command line: Missing command script file
| Cause: | The use of a command script file is required. | |
| Action: | Create a command script file. If a file already exists, enter the correct filename and check your path. | |
Refer to EBU Administrator's Guide for more details.
EBU-111 Error in command line: string is not a valid option
| Cause: | Specified option is not recognized by Enterprise Backup Utility. | |
| Action: | Specify a valid option. | |
Refer to EBU Administrator's Guide for more details.
EBU-112 WARNING: Cannot run in silent mode, log file was not specified.
| Cause: | A log file is needed when silent option is used. | |
| Action: | Please specify a log file in the command script file or do notuse the silent option. This is a warning, the output will go to standard error. | |
Refer to EBU Administrator's Guide for more details.
EBU-113 Error: REGISTER command cannot be used with -test
| Cause: | Test option is not valid during registration. | |
| Action: | Please do not use test option when registering. | |
Refer to EBU Administrator's Guide for more details.
EBU-114 Error: -noautoregister is only valid for Backup Online jobs
| Cause: | Autoconfiguration feature is only used when performing online backups, thus it cannot be disabled for other types of operations. | |
| Action: | Do not use this feature for the specified operation. | |
Refer to EBU Administrator's Guide for more details.
EBU-115 Error: Cannot specify -test and -checksum at the same time
| Cause: | Dry run tests do not perform I/O. Checksums are calculated while performing I/O. Thus these options are mutually exclusive and cannot be specified at the same time. | |
| Action: | Please remove either test or checksum option for the operation to proceed. | |
Refer to EBU Administrator's Guide for more details.
EBU-116 Error: Extra command script specified: script_name
| Cause: | More than one command script file was specified or an option was specified without the a dash (-). | |
| Action: | Remove the extra command script file or put a dash (-) in frontof the specified option. | |
Refer to EBU Administrator's Guide for more details.
EBU-500 Error in memory allocation
| Cause: | Enterprise Backup Utility required some memory and there is no memory available in the system. | |
| Action: | This is normally caused by insufficient swap space in the system. Verify the amount of swap space available. The system might run out of swap space for brief periods of time, so retrying the operation might succeed. If the error is consistent and there is sufficient free swap space, report this problem. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-501 Error, name string is too long; it must be at most length_limit characters
| Cause: | The internal buffer for the specified string is not big enough to hold it. | |
| Action: | The internal buffers have been sized for legal values. If a legal value for the specified parameter is being used, report this problem. | |
Refer to EBU Administrator's Guide for more details.
EBU-502 Error, password is too long; it must be at most length_limit characters
| Cause: | The internal buffer for the password is not big enough tohold the specified value. | |
| Action: | An Oracle password cannot exceed 30 characters. | |
Refer to Oracle7 Server Administrator's Guide for more details.
EBU-503 Additional operating system information, error error_number: error_string
| Cause: | An error during an operating system operation was detected, this error is the cause of the preceding error. | |
| Action: | Please correct the operating system error before retrying the operation. If unable to determine the underlying operating system error, contact your System Support Engineer. | |
Refer to your operating system documentation.
EBU-504 SQL error error_string
| Cause: | Previous operation had an Oracle error. Text of error is displayed. | |
| Action: | Lookup the SQL error in Oracle7 Server Messages and follow the suggested action. | |
Refer to Oracle7 Server Administrator's Guide or contact Oracle Worldwide Support with the log file for the operation.
EBU-505 Occurred in the following SQL statement: SQL_error in filename: file_name at line number: line_number
| Cause: | See previous error messages | |
| Type: | See types for previous errors. | |
None
EBU-506 Operating system error opening disk file file_name
| Cause: | Enterprise Backup Utility tried to open a disk file and received an error from the operating system. | |
| Action: | The additional operating system error information should help to pinpoint the cause of the problem. Rectify and retry operation. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-507 Operating system error while seeking position on disk file file_name
| Cause: | Enterprise Backup Utility tried to move internal file pointer of a disk file and received an error from the operating system. | |
| Action: | The additional operating system error information should help to pinpoint the cause of the problem. Rectify and retry operation. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-508 Operating system error while reading disk file file_name
| Cause: | Enterprise Backup Utility tried to read from a disk file and received an error from the operating system. | |
| Action: | The additional operating system error information should help to pinpoint the cause of the problem. Rectify and retry operation. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-509 Error detected while performing header verification tests on file file_name; file is probably corrupted
| Cause: | The header file does not match Oracle specification or is corrupted. | |
| Action: | Check header file. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-510 Operating system errors detected while initializing interprocess messages
| Cause: | Enterprise Backup Utility encountered an error from the operating system. | |
| Action: | Report the error with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-511 Operating system errors detected while attaching to shared memory
| Cause: | Enterprise Backup Utility encountered an error from the operating system. | |
| Action: | Report the error with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-512 Operating system error while setting signal handler for SIGALRM
| Cause: | Enterprise Backup Utility encountered an error from the operating system. | |
| Action: | Report the error with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-513 Operating system error while setting signal handler for SIGCHLD
| Cause: | Enterprise Backup Utility encountered an error from the operating system. | |
| Action: | Report the error with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-514 Operating system error detected while receiving WORK message
| Cause: | Enterprise Backup Utility encountered an error from the operating system. | |
| Action: | Report the error with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-515 Operating system Error in sigset of SIGHUP
| Cause: | Enterprise Backup Utility encountered an error from the operating system. | |
| Action: | Report the error with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-516 Internal error. Process process_ID has exited abnormally
| Cause: | Possibly caused by an operating system error or a kill command. | |
| Action: | Report the error with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-517 Error while retrieving BFS information of job job_ID from catalog database
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file.. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-518 Error, read on database file file_name, returned number bytes, expecting multiple of number.
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-519 Error in removing BFS file_name of job job_ID
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-520 BFS file_name of job job_ID removed successfully from backup media
None
EBU-521 Error in catalog interface, return code is an invalid status: return_code
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-522 Could not allocate number bytes
| Cause: | System ran out of memory resource. | |
| Action: | Add more memory, kill unwanted processes to free up memory. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-523 Username:
None
EBU-524 Password:
None
EBU-525 Connect String:
None
EBU-526 Please input information to login to target database
None
EBU-527 An empty return indicates to use internal user with default local connection
None
EBU-530 Date date is not in expected format: MM/DD/YYYY [HH24:MI:SS]
Refer to EBU Administrator's Guide for more details.
EBU-531 Specified day in date is not valid
Refer to EBU Administrator's Guide for more details.
EBU-532 Specified month in date is not valid
| Cause: | Month format error. | |
Refer to EBU Administrator's Guide for more details.
EBU-533 Specified year in date is not valid
Refer to EBU Administrator's Guide for more details.
EBU-534 Specified hours in date are not valid
Refer to EBU Administrator's Guide for more details.
EBU-535 Specified minutes in date are not valid
| Cause: | Minute format error. | |
Refer to EBU Administrator's Guide for more details.
EBU-536 Specified seconds in date are not valid
| Cause: | Second format error. | |
Refer to EBU Administrator's Guide for more details.
EBU-1001 User structure has not been initialized
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1002 Previously allocated blocks have not been released
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1003 Disk number does not match
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1004 No blocks to release
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1005 Error: Inconsistent shared buffer bitmap
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1006 Error: Inconsistent User structure
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1007 Number of tape processes exceeds buffer areas allocated
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1008 Error: inconsistent buffer area read/write pointer
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1009 Error: number of disks assigned to the buffer area greater than allocated
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1010 Error: inconsistent buffer area header structure
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1011 Brbrfret: incorrect file number
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1012 Incorrect number of blocks to release
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1013 Incorrect memory address to attach shared buffer
| Cause: | Memory corruption or internal programming error. | |
| Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1500 Instance Manager (BRD) with process_ID successfully started on hostname
None
EBU-1501 Instance Manager (BRD) with process_ID exited on hostname
None
EBU-1502 Instance manager with process_ID exiting on hostname, errors detected during execution
| Cause: | This means that one or more errors were detected during the run of the Instance Manager. Review the log file to find out the details of them. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1503 Error while disconnecting from catalog database
| Cause: | Catalog database had an Oracle error. | |
| Action: | Correct the Oracle error before starting a new EBU job. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1504 Error while retrieving active jobs from catalog database
| Cause: | Catalog database had an Oracle error while reading active jobs. | |
| Action: | Correct the Oracle error. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1505 Instance Manager is not recorded in catalog anymore, aborting...
| Cause: | Catalog database had an Oracle error when reading Instance Manager record from catalog database. If a row not found error is returned, this is normally caused by deleting the catalog from underneath a running Instance Manager. | |
| Action: | Correct the Oracle error. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1506 Error while verifying status of job job_ID in catalog database
| Cause: | Catalog database had an Oracle error while retrieving information about a job to determine if it was still active or it had crashed. | |
| Action: | Correct the Oracle error | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1507 Error while updating job job_ID status in catalog database
| Cause: | Catalog database had an Oracle error while updating information about a crashed job. | |
| Action: | Correct the Oracle error. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1508 Error while verifying tablespaces of job job_ID in catalog database
| Cause: | Catalog database had an Oracle error while retrieving information about the tablespaces affected by a backup job. | |
| Action: | Correct the Oracle error. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1509 Error while trying to clean tablespace tablespace_name of job job_ID
| Cause: | A crashed backup job left this tablespace in BACKUP mode. The Instance Manager tried to connect to target database and issue 'ALTER TABLESPACE ... END BACKUP' and found an error while doing so. The tablespace will be cleaned after next startup. This error normally is not a cause for concern. | |
| Action: | Report it if this error is happening frequently. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1510 Tablespace tablespace_name of job job_ID successfully cleaned
None
EBU-1511 Finished cleaning job job_ID
None
EBU-1512 Instance Manager terminated by explicit user request
None
EBU-1513 Error while setting handler for signals to be ignored
| Cause: | This message should not normally be issued. There was an operating system error while setting the signal handler. Look at the description of the operating system error for more details. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1514 Error while setting handler for termination
| Cause: | This message should not normally be issued. There was an operating system error while setting the signal handler for SIGTERM, look at the description of the operating system error for more details. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1515 Error while verifying status of process_ID of job job_ID
| Cause: | This message should not normally be issued. There was an operating system error while using kill system call to detect if a pid was still alive. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1516 Error while removing IPC resources, shkey = number. This will have to be cleaned up manually
| Cause: | This message should not normally be issued. There was an operating system error while using the shmdt and semctl function calls. More information will be output to trace. Out of sync objects might produce this error. | |
| Action: | Relink all executables and retry if it has not been done. Report with runtime operating system configuration if problem persists. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1517 Error while manipulating handler for wakeup signal, additional info=number
| Cause: | This message should not normally be issued. There was an operating system error while setting the signal handler for SIGUSR1, look at the description of the operating system errorfor more details. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1518 Error while connecting to catalog database
| Cause: | Catalog database had an Oracle error when connecting to it. Most of the time this would be caused because the catalog database has not been started or the protocol listener has not been started. | |
| Action: | Correct the Oracle error | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1519 Process has reached the idle time limit and will proceed to shutdown itself
None
EBU-1520 Error during Instance Manager initialization, exiting
| Cause: | Above errors prevented the Instance Manager from completing basic initialization. Instance Manager cannot run, thus is exiting. | |
| Action: | Correct above errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1521 Preceding errors prevent normal operation, exiting immediately
| Cause: | Could not establish handler for SIGUSR1 signal which is basic for operation, so the Instance Manager has to exit immediately. | |
| Action: | Correct above errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1522 Error in variable_name environment variable value, will use default for parameter
| Cause: | Specified value for environment variable is negative or not a number. | |
| Action: | Use a positive number. | |
Refer to EBU Administrator's Guide for more details.
EBU-1523 Total idle time for set to number seconds
None
EBU-1524 Active jobs will be monitored each number seconds if no errors are detected
None
EBU-1525 Active jobs will be monitored each number seconds when errors are detected
None
EBU-1526 Process will be reniced to run at -nice_value
None
EBU-1527 Retry number times before hibernating
None
EBU-1528 Error while retrieving hostname information
| Cause: | This message should not normally be issued. There was an operating system error while retrieving the host name error for more details. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1529 Previous errors prevent running of Instance Manager (brd), exiting
| Cause: | The Instance Manager needs to register itself in the catalog database. Previous errors prevented this, thus exiting. | |
| Action: | Correct above errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1530 Error: another Instance Manager process is active (process_ID), will wake it up
| Cause: | Another Instance Manager is registered in the catalog and is still active. A second Instance Manager cannot be started. This message should not normally be issued, unless the brd executable is invoked directly as opposed to started automatically by obackup executable. | |
| Action: | Do not invoke brd executable directly. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1531 Error registering Instance Manager process in the catalog
| Cause: | Catalog database had an Oracle error when inserting Instance Manager record into the catalog database. | |
| Action: | Correct the Oracle error. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1532 Error while updating brd entry in catalog database
| Cause: | Catalog database had an Oracle error when updating Instance Manager record in the catalog database. | |
| Action: | Correct the Oracle error. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1533 Error while updating cleaned job history in the catalog
| Cause: | Catalog database had an Oracle error when updating the job history table record in the catalog database. | |
| Action: | Correct the Oracle error. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1534 Given up cleaning job job_ID, max number of retries number reached
| Cause: | This message should not normally be issued. The Instance Manager has repeatedly tried to cleanup the specified jobid unsuccesfully, will not try anymore. | |
| Action: | This is an informational message; the real errors should have been logged. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1535 Error while obtaining Instance Manager semaphore set
| Cause: | This message should not normally be issued. The Instance Manager could not obtain the semaphores needed for its operation. | |
| Action: | This is most likely due to limited semaphore resources in the system. Reconfigure the kernel and try again. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1536 Error while updating Instance Manager semaphore set (number) by proces_ID
| Cause: | This message should not normally be issued. The Instance Manager could not manipulate the semaphore set used to control its operation. Look at the description of the operating system error for more details. | |
| Action: | Verify the presence of the semaphore set in the system. If set is not available, an external event has removed it thus causing the error. If semaphore set is available, then the number of UNDO structures in the system has been exceeded. Reconfigure the kernel and try again. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1537 Error while manipulating handler for timing signal, additional info=number
| Cause: | This message should not normally be issued. There was an operating system error while setting the signal handler for SIGALRM. Look at the description of the operating system error for more details. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-1538 Proceeding to clean failed job job_ID
| Cause: | The Instance Manager has found a job that needs to be cleaned and is proceeding to do so. | |
None
EBU-2000 Job job_ID failed due to buffer management error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2001 Job job_ID failed due to operating system error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2002 Job job_ID failed due to target database error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2003 Job job_ID failed due to an internal error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2004 Job job_ID failed due to corrupted header
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2005 Job job_ID failed due to read errors from disk or tape
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2006 Job job_ID failed due to Tape API (sbt) error on vendor side
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2007 Job job_ID failed due to write error to disk
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2008 Job job_ID failed due to a messaging error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2009 Job job_ID failed due to a parameter error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2010 Job job_ID failed due to an invalid syntax
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2011 Job job_ID failed due to bitmap manipulation error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2012 Job job_ID failed due to tape management error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2013 Job job_ID failed due to an environmental (external) error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2014 Job job_ID failed due to a catalog error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2015 Job job_ID failed due to permission/security error
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2016 Job job_ID failed due to being cancelled by user request
None
EBU-2017 REGISTER job SUCCESSFUL
None
EBU-2018 BACKUP job SUCCESSFUL
None
EBU-2019 Job job_ID with process_ID completed on hostname
None
EBU-2020 REGISTER job FAILED
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file.. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2021 Job job_ID was CANCELLED
None
EBU-2022 DRY TEST RUN: No backup/restore output will be generated
None
EBU-2023 Test specified: No job execution is to be performed
None
EBU-2024 Cannot cancel job job_ID, operating system process process_ID is not running
| Cause: | User is trying to cancel a non-existent job. | |
| Action: | Correct the error. | |
Refer to EBU Administrator's Guide for more details.
EBU-2025 Connected to catalog database
None
EBU-2026 Error in disconnecting from catalog database
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file.. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2027 Disconnected from catalog database
None
EBU-2028 Error while obtaining operating system information for job = job_ID from catalog database
| Cause: | An error was returned by system call function. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2029 Error while cancelling operating system process process_ID for job job_ID
| Cause: | An error was returned by system call function. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2030 CANCEL message successfully sent to job job_ID on hostname
None
EBU-2031 This restore will require archive logs starting with sequence number number
None
EBU-2032 Error while waiting for job job_ID to be cancelled
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2033 Registration failed
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2034 RESTORE job SUCCESSFUL
None
EBU-2035 BACKUP job FAILED
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2036 RESTORE job FAILED
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2037 Started invalidation of job job_ID at hostname
None
EBU-2038 Catalog error while invalidating job job_ID
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2039 Media management error while invalidating job job_ID
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
MML Vendor Support with the log file for the operation.
EBU-2040 Previous errors do not allow job job_ID to be invalidated
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2041 Finished invalidation of job job_ID at hostname
None
EBU-2042 INVALIDATE job SUCCESSFUL
None
EBU-2043 INVALIDATE job FAILED
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2044 CANCEL job SUCCESSFUL
None
EBU-2045 CANCEL job FAILED
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2046 Started cancellation of job job_ID at hostname
None
EBU-2047 Finished cancellation of job job_ID at hostname
None
EBU-2048 Job job_ID failed; exit code = error_code
| Cause: | Summary error message. Error messages leading to it should have been recorded in the log file. | |
| Action: | Refer to actions for causal errors. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2049 Waiting for job job_ID to finish cancellation (it might be a while)
None
EBU-2050 Error calling sbtinit for tape management software
| Cause: | This error is caused by media management layer software. | |
| Action: | Contact your media management software vendor. | |
Media Management software Vendor Support
EBU-2053 Usage: obackup [ [{ -ch[ecksum] | -t[est] }] | -noa[utoregister] | -s[ilent] | -ob[k_home]=<path> ] <command_filename>
Refer to EBU Administrator's Guide for more details.
EBU-2054 Error opening file file_name to read catalog connect string
| Cause: | EBU fails to open catalog configuration file. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2055 Error reading catalog database connect string
| Cause: | EBU failed to read catalog configuration file. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2057 Tape API: Release number
None
EBU-2058 Tape Management Software: Release release_number
None
EBU-2059 Error reading from console
| Cause: | No console is attached to EBU (when register database) or user hits Ctrl-C to interrupt input. | |
| Action: | Start up a console and run EBU from it as foreground process. | |
Refer to EBU Administrator's Guide for more details.
EBU-2100 File file_name to be remapped is not on job list
| Cause: | Filename is not specified correctly. | |
Refer to EBU Administrator's Guide for more details.
EBU-2101 File file_name remapped twice
| Cause: | Filename is specified twice. | |
Refer to EBU Administrator's Guide for more details.
EBU-2102 Using database information registered on hostname
None
EBU-2103 Starting job building. Involved files are:
None
EBU-2104 Saving current control file file_name as backup control file file_name
None
EBU-2105 Disk, tape I/O or buffer size must be set to power of 2
| Cause: | the parameters (DISK_IO_SIZE, TAPE_IO_SIZE, BUFFER_SIZE) are not set correctly. | |
Refer to EBU Administrator's Guide for more details.
EBU-2106 Since no database files are being backed up, control file will not be backed up
None
EBU-2107 Error removing file filename
| Cause: | An error was returned by system call to remove file. | |
| Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2108 File file_name will be restored as file_name
None
EBU-2109 Control file file_name will be restored as file_name
None
EBU-2110 Starting ARCHIVELOG file building:
None
EBU-2111 Archive log directory directory_name
None
EBU-2112 Archive log file file_name
None
EBU-2113 A restore job with target database offline needs a directory destination to restore archive logs
| Cause: | No directory is set in the parameter for archive log files. | |
| Action: | Specify a directory. | |
Refer to EBU Administrator's Guide for more details.
EBU-2114 Ending ARCHIVELOG file building
None
EBU-2115 Archive log files will be restored to directory directory_name
None
EBU-2116 Archive log files will be restored to their original backup locations
None
EBU-2117 Error obtaining archive log information from catalog database
| Cause: | Oracle database error. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2118 Archive log file file_name found in
None
EBU-2119 Database files are obtained from jobs job_ID to job_ID
None
EBU-2120 Archive log files are obtained from jobs job_ID to job_ID
None
EBU-2121 No archive logs need to be restored to disk, all are accounted for
None
EBU-2122 Datafile file_name
None
