
CHAPTER 1. Enterprise Backup Utility Messages
EBU-2123 Control file file_name
None
EBU-2124 Parameter file file_name
None
EBU-2125 Backup File Set file_name
None
EBU-2126 Backup File Set file_name from backup job job_ID
None
EBU-2127 No files to backup/restore for job
Cause: | No files were specified for EBU job. | |
Refer to EBU Administrator's Guide for more details.
EBU-2128 Error expanding file file_name with ORACLE_SID and ORACLE_HOME
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2129 The database parameter file file_name specified cannot be accessed
Cause: | File does not exist, or incorrectly specified. | |
Refer to EBU Administrator's Guide for more details.
EBU-2130 No control files among backup file list; registration error
Cause: | File does not exist, or incorrectly specified. | |
Refer to EBU Administrator's Guide for more details.
EBU-2131 File file_name cannot be multiplexed; only datafiles can be multiplexed
Cause: | Non-datafiles are included in the mux file list | |
Action: | Remove non-datafiles from mux file list | |
Refer to EBU Administrator's Guide for more details.
EBU-2132 Too many multiplexed files specified for BFS
Cause: | Too many datafiles are included in the mux file list. EBU imposes 32 as the absolute upper limit. Operating system may impose upper limit less than 32. | |
Refer to EBU Administrator's Guide for more details.
EBU-2133 File file_name to be multiplexed is not on backup file list, or it might have been processed already
Cause: | File was not included in backup file list, but it was in multiplex file list, which is not allowed. Or it was in another multiplex file list already. | |
Refer to EBU Administrator's Guide for more details.
EBU-2134 Multiplexed datafile file_name on BFS backup_fileset_number
None
EBU-2135 Not sufficient privileges to back up file_name
Cause: | The user tried to run EBU without sufficient privileges. | |
Action: | Run EBU with sufficient privileges. | |
Refer to EBU Administrator's Guide for more details.
EBU-2136 Not able to restore to file_name; please check permissions
Cause: | User did not have permissions to restore. | |
Refer to EBU Administrator's Guide for more details.
EBU-2137 WARNING: Length of string should be number bytes and not number bytes
Cause: | Registration information is out of date. | |
Action: | Reconfigure the catalog by registering your target database. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2138 WARNING: Permission of db_name does not match catalog information
Cause: | Registration information is out of date. | |
Action: | Reconfigure the catalog by registering your target database. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2139 One or more parameters specified is not within valid range
Cause: | Parameter out of range. | |
Refer to EBU Administrator's Guide for more details.
EBU-2140 Error obtaining hostname information
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2141 Ending job building
None
EBU-2142 Error accessing the specified archive log directory directory_name
Cause: | Archive log directory is not correctly specified. | |
Refer to EBU Administrator's Guide for more details.
EBU-2143 Archive log file file_name cannot be accessed
Cause: | Archive log file is not correctly specified. | |
Refer to EBU Administrator's Guide for more details.
EBU-2144 WARNING: Database information registered on hostname not verified to be up to date.
None
EBU-2145 Please be sure to use the REGISTER command to update the backup catalog if there are any changes
None
EBU-2146 Do not specify -noautoconfigure if you want the database information to be automatically verified
None
EBU-2147 Internal error, Instance Manager was not able to cleanup failed job job_ID. Reason might be found in $OBK_HOME/log/brd.log
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-2148 Waiting for failed job job_ID to be cleaned...
None
EBU-2149 Requesting Instance Manager to cleanup failed job job_ID
None
EBU-2150 Operating system error detected while contacting Instance Manager (number) to cleanup 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-2219 Error setting up signal handlers
Cause: | An error was returned by system call to set up signal handler. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2220 Archive log file file_name deleted
None
EBU-2221 Too many incoming signals, queue overflow
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2222 Cancel request received
None
EBU-2223 User interrupted job
None
EBU-2224 No archive log files will be restored
None
EBU-2225 Error setting special semaphore number in set number for crash detection
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2226 No archive log files found at destinations to backup
Cause: | Archive log file destination was not specified correctly | |
Refer to EBU Administrator's Guide for more details.
EBU-2227 Error initializing shared buffer; probably out of memory
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-2228 Error spawning brio process
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-2229 Error sending INIT message to brio process process_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-2230 Error receiving acknowledgment of INIT message from process process_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-2231 Error in acknowledgment of INIT message
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-2232 Brio indicated failure in acknowledgement of INIT message
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-2235 Fatal error: all brio's have exited for unknown reasons
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2236 Starting backing up to tape
None
EBU-2237 Starting restoring to disk
None
EBU-2238 Total shared memory used: number bytes
None
EBU-2239 Checksum mismatch for backup file set backup_fileset_name: number vs. number
Cause: | Tape media failure. | |
Action: | Make sure tape is not corrupted/damaged. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2240 File file_name failed header verification tests after restore
Cause: | Tape media failure. | |
Action: | Make sure tape is not corrupted/damaged. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2241 Disk input/output size: number bytes
None
EBU-2242 Buffer size per I/O stream: number bytes
None
EBU-2243 Number of parallel I/O streams: number
None
EBU-2244 WARNING: buffer specified is too small; set to number bytes
Cause: | Buffer size must be at least as large as DISK_IO_SIZE. | |
Refer to EBU Administrator's Guide for more details.
EBU-2245 Maximum tape I/O size: number bytes
None
EBU-2246 Completing backing up to tape
None
EBU-2247 Completing restoring to disk
None
EBU-2248 Error holding signals from child processes
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2249 Error releasing signals to child processes
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2250 WARNING: archivelog files have not been backed up
None
EBU-2251 Use BACKUP ONLINE ARCHIVELOG command to backup archivelog files in another job
None
EBU-2252 Recovery to current point might not be possible if archivelog files are lost
None
EBU-2255 Error sending BACKUP WORK message to brio (message_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-2266 Received FAILURE message from brio; errcode = 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-2281 Received unknown message; type = mesage_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-2339 Error cleaning up shared memory and IPC
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-2345 Error in final shutdown of brio (process process_ID); errno = 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-2350 Error in wait
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2354 Brio terminated abnormally
Cause: | Internal error or caused by kill command by user. | |
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2450 Found Instance Manager (brd) process running with process process_ID
None
EBU-2453 Error while obtaining information about Instance Manager in catalog
Cause: | Catalog database had an Oracle error when looking for Instance Manager record in the catalog database. | |
Action: | Correct the Oracle error. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2455 Error while updating information about Instance Manager 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-2456 Error while forking Instance Manager process (brd)
Cause: | There was an operating system error while using fork system call. Common reasons are: the number of allowed process in the system or per user is exceeded or the swap are is full. Look at the description of the operating system error for more details. | |
Action: | Report the error with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2457 Error while executing Instance Manager process (brd)
Cause: | There was an operating system error while using execv system call. A common reason for this error is the lack of the brd executable ($OBK_HOME/bin/brd). This can be caused by a non-succesful installation or relink which either did not create the brd executable or created a non valid executable image. Other problems could be permissions, like an executable without execute permissions | |
Action: | Report the error with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2458 Error while waiting for Instance Manager process (brd)
Cause: | This message should not normally be issued, except in conjunction with errors during exec. There was an operating system error while waiting for brd to become a detached process, 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-2459 Instance Manager not running, starting a new one
None
EBU-2460 Verifying presence of Instance Manager process...
None
EBU-2461 Error while updating work semaphore number of Instance Manager process (process_ID). A new Instance Manager will be started
Cause: | This message should not normally be issued. There was an operating system error while using semctl system calls to update the semaphore for the Instance Manager. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2462 Instance Manager (BRD, process_ID) was terminated
None
EBU-2463 New Instance Manager (brd) process started with pid = process_ID
None
EBU-2464 Internal error. Instance Manager process was not started
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-2550 Error opening command script file file_name
Cause: | Command script not specified correctly. | |
Refer to EBU Administrator's Guide for more details.
EBU-2551 Error initializing job structure
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2552 Error detected in command script
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-2553 Error completing job structure
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2554 File file_name line number:
Cause: | An error occur at specified location. | |
Action: | Correct it (using the error messages that followed). | |
Refer to EBU Administrator's Guide for more details.
EBU-2555 Missing parameter_name parameter
Cause: | A parameter was missing. | |
Action: | Specifiy parameter needed. | |
Refer to EBU Administrator's Guide for more details.
EBU-2556 Parameter_name parameter invalid for this command
Cause: | A parameter was not correctly specified. | |
Action: | Specifiy parameter as indicated. | |
Refer to EBU Administrator's Guide for more details.
EBU-2557 You may not specify parameter_name parameter with TABLESPACE parameter
Cause: | A parameter was not correctly specified. | |
Action: | Specifiy parameter as indicated. | |
Refer to EBU Administrator's Guide for more details.
EBU-2558 Expected one of BACKUP, RESTORE, REGISTER, INVALIDATE or CANCEL commands
Refer to EBU Administrator's Guide for more details.
EBU-2559 WARNING: duplicate parameter_name parameter
Cause: | The same parameter was included multiple times. | |
Refer to EBU Administrator's Guide for more details.
EBU-2560 File_name unexpected
Refer to EBU Administrator's Guide for more details.
EBU-2561 You must specify OFFLINE or ONLINE for a backup command
Refer to EBU Administrator's Guide for more details.
EBU-2562 At least one of DATABASE, CONTROL_FILE, PFILE, TABLESPACE, DBFILE, or ARCHIVELOG must be specified
Refer to EBU Administrator's Guide for more details.
EBU-2563 At least one of CONTROL_FILE, PFILE, TABLESPACE, DBFILE, or ARCHIVELOG must be specified
Refer to EBU Administrator's Guide for more details.
EBU-2564 Partial offline backup is not yet supported
Cause: | User specified a unsupported feature. | |
Refer to EBU Administrator's Guide for more details.
EBU-2565 Error opening parameter file file_name
Cause: | Parameter file is not specified correctly. | |
Refer to EBU Administrator's Guide for more details.
EBU-2566 Too many parameter files opened
Cause: | Number of parameter files exceeds operating system limit. | |
Refer to EBU Administrator's Guide for more details.
EBU-2567 Double-quoted string expected
Refer to EBU Administrator's Guide for more details.
EBU-2568 Number expected
Refer to EBU Administrator's Guide for more details.
EBU-2569 "=" expected
Refer to EBU Administrator's Guide for more details.
EBU-2570 string should be in double quotes
Refer to EBU Administrator's Guide for more details.
EBU-2571 WARNING: string should be in double quotes
Refer to EBU Administrator's Guide for more details.
EBU-2572 WARNING: TAPE_IO_SIZE parameter is ignored for RESTORE
Refer to EBU Administrator's Guide for more details.
EBU-2573 WARNING: missing parentheses; datafiles separated with commas will be multiplexed together
Refer to EBU Administrator's Guide for more details.
EBU-2574 WARNING: missing start parenthesis; datafiles separated with commas until end parenthesis will be multiplexed together
Refer to EBU Administrator's Guide for more details.
EBU-2575 WARNING: missing end parenthesis. The group of datafiles separated with commas will be multiplexed together
Refer to EBU Administrator's Guide for more details.
EBU-2576 WARNING: more than one directory specificed for restore archivelog. Directory directory_name unused
Cause: | Only one archivelog directory is used for restore. | |
Refer to EBU Administrator's Guide for more details.
EBU-2577 Start_lsn expected with ARCHIVELOG when using RESTORE ARCHIVELOG or RESTORE DATABASE CONSISTENT
Refer to EBU Administrator's Guide for more details.
EBU-2578 Both archivelog directory and ARCHIVELOG = NONE are used
Refer to EBU Administrator's Guide for more details.
EBU-2579 ARCHDELETE cannot be used with ARCHIVELOG=NONE
Refer to EBU Administrator's Guide for more details.
EBU-2580 WARNING: missing end quote
Refer to EBU Administrator's Guide for more details.
EBU-2581 WARNING: null string specified
Refer to EBU Administrator's Guide for more details.
EBU-2582 WARNING: null regular expression specified
Refer to EBU Administrator's Guide for more details.
EBU-2600 Error creating catalog database record
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-2601 Error creating tablespace tablespace_name
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-2602 Operating system error obtaining timestamp
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2603 Error registering tablespace tablespace_name in catalog
Cause: | An Oracle error was encountered | |
Action: | Fix the Oracle error before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2604 No control file specified
Cause: | An Oracle error was encountered. | |
Action: | Fix the Oracle error before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2605 Error getting sequence number sequence_number
Cause: | An Oracle error was encountered. | |
Action: | Fix the Oracle error before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2606 Error registering control file information in catalog
Cause: | An Oracle error was encountered. | |
Action: | Fix the Oracle error before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2607 No parameter file specified
Cause: | An Oracle error was encountered. | |
Action: | Fix the Oracle error before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2608 Error registering parameter file information in catalog
Cause: | An Oracle error was encountered. | |
Action: | Fix the Oracle error before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2609 Unable to find a Backup Offline for Database db_name in catalog
Cause: | User attempted to restore a database without a offline backup. | |
Refer to EBU Administrator's Guide for more details.
EBU-2610 Illegal block size, number
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-2611 Illegal RLC (current rlc=number catalog rlc=number): usually from not updating registration after OPEN RESETLOGS
Cause: | Either is caused by out of date registration information or internal. | |
Action: | File a bug if it is internal. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2612 Error creating catalog entries for Backup File Sets
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-2613 Null argument
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2614 Illegal user/password string
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-2615 Cannot restore archived log files due to tape I/O incompatibility with main job: number vs. number
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-2616 Error fetching target database information from the catalog
Cause: | An Oracle error occured | |
Action: | Fix it before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2617 Error fetching file information from the catalog
Cause: | An Oracle error occured | |
Action: | Fix it before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2618 Error fetching tablespace information from the catalog
Cause: | An Oracle error occured | |
Action: | Fix it before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2619 Illegal job type, number
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2620 Illegal file type specified
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2621 Error obtaining jobid for requested start_lsn number for dbid db_ID
Cause: | An Oracle error occured or start log sequence number is not specified correctly | |
Action: | Fix it before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2622 Error obtaining jobid for latest backup job to restore archive logs for dbid db_ID
Cause: | An Oracle error occured | |
Action: | Fix it before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2623 Error allocating memory
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-2624 Error substituting oracle variables in string
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2625 Error adding file file_name to list
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-2626 WARNING: Cannot find backed up archive log files in catalog database
Cause: | Archive log files were not specified correctly | |
Refer to EBU Administrator's Guide for more details.
EBU-2627 SQL statement failed. SQL_statement - sqlerror=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-2628 Duplicate file specified, file_name is a member of tablespace tablespace_name
Cause: | Duplicate files specified | |
Refer to EBU Administrator's Guide for more details.
EBU-2629 No file specified
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2630 Duplicate file name specified, filename
Cause: | Duplicate files specified. | |
Refer to EBU Administrator's Guide for more details.
EBU-2631 Duplicate tablespace specified, tablespace_name
Cause: | Duplicate tablespace specified. | |
Refer to EBU Administrator's Guide for more details.
EBU-2632 Empty list
Refer to EBU Administrator's Guide for more details.
EBU-2633 ORACLE_HOME not set
Cause: | ORACLE_HOME not set. | |
Refer to EBU Administrator's Guide for more details.
EBU-2634 ORACLE_SID not set
Cause: | ORACLE_SID not set. | |
Refer to EBU Administrator's Guide for more details.
EBU-2635 Hostname not set
Refer to EBU Administrator's Guide for more details.
EBU-2636 Insufficient memory available
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-2637 Illegal or null date specified: date
Cause: | Illegal or null date specified. | |
Refer to EBU Administrator's Guide for more details.
EBU-2638 Illegal or null db_name specified
Cause: | Illegal or null db_name specified. | |
Refer to EBU Administrator's Guide for more details.
EBU-2639 Illegal or null BFS name specified
Cause: | Illegal or null BFS name specified | |
Refer to EBU Administrator's Guide for more details.
EBU-2640 File names do not match: file_name and filename
Cause: | Filenames do not match. | |
Refer to EBU Administrator's Guide for more details.
EBU-2641 Creation dates do not match for SID=sid
Cause: | Creation dates do not match. | |
Refer to EBU Administrator's Guide for more details.
EBU-2642 Error creating BFS for file file_name
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-2643 Error adding file file_name to BFS backup_fileset_name
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-2644 Unable to find a backup for file file_name
Cause: | File is not specified correctly. | |
Action: | Correct it. Use ebucatutl to check for backup file list. | |
Refer to EBU Administrator's Guide for more details.
EBU-2645 BFS or DB information in catalog appears to be corrupted
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2646 Unable to get/create BFS backup_fileset_name
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-2648 Error obtaining information for Restore Database Consistent
Cause: | An Oracle error occurred. | |
Action: | Fix it before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2650 Unable to find job job_ID in the catalog
Cause: | Job_id was not specified correctly. | |
Refer to EBU Administrator's Guide for more details.
EBU-2651 Illegal object type
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2653 Failed job job_ID has tablespace tablespace_name locked
None
EBU-2654 Unable to find a backup for all the files of tablespace tablespace_name, list follows
Cause: | User tried to restore a tablespace without all datafiles backed up. | |
Refer to EBU Administrator's Guide for more details.
EBU-2655 Error inserting file file_name information into the catalog
Cause: | An Oracle error occurred. | |
Action: | Fix it before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2656 Fatal error: bad process identifier (pid) for current execution: process_ID
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2657 Illegal semaphore identifier: number
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2658 Illegal semaphore number: number
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2659 Illegal shared memory identifier: number
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2660 Row not found: string
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2661 Row already exists: table=table_name id=number
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2662 Cannot shutdown Instance Manager. Illegal reason
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2664 Could not get lock for dbid=db_ID
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2665 Error obtaining information for Restore job
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-2666 Job job_ID is running and has tablespace tablespace_name locked. Please either cancel job job_ID or wait until it is completed
None
EBU-2670 User specified tablespace=tablespace_name does not exist for ORACLE_SID=sid in catalog
Cause: | Tablespace does not exist. | |
Refer to EBU Administrator's Guide for more details.
EBU-2671 User specified file=file_name does not exist for ORACLE_SID=sid in catalog
Cause: | File does not exist. | |
Refer to EBU Administrator's Guide for more details.
EBU-2672 Cannot lock table table_name after several retries, giving up
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2673 Cannot invalidate a non-successful job, current state of job job_ID is: number
Cause: | Invalidate a non-successful job is not allowed. | |
Refer to EBU Administrator's Guide for more details.
EBU-2674 Invalid state (number) for job job_ID
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2675 Invalid state (job_state) for tsid=number
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2676 Invalid state (number) from catalog for tsid=number
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2677 Cannot update job job_ID to terminal state due to catalog inconsistency. Aditional info: number, number
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2678 Cannot invalidate a non-backup job, type of job job_ID is number
Cause: | Invalidating a non-backup job is not allowed | |
Refer to EBU Administrator's Guide for more details.
EBU-2679 Job job_ID is already being invalidated in another job
Cause: | Job is being invalidated in another job | |
Refer to EBU Administrator's Guide for more details.
EBU-2680 Database db_name - string is not registered in catalog, please use REGISTER command before attempting this operation
Cause: | Database not registered | |
Refer to EBU Administrator's Guide for more details.
EBU-2681 Registering target database in catalog database
None
EBU-2682 Target database registered in catalog database on hostname
None
EBU-2683 Parameter file file_name
None
EBU-2684 Tablespace tablespace_name
None
EBU-2685 Datafile file_name
None
EBU-2686 Control file file_name
None
EBU-2687 ORA-number is normally caused by: a) procedural option not installed or b) catproc.sql not run in catalog database
Cause: | This error usually occurs due to component specified not installed for catalog database. | |
Refer to EBU Administrator's Guide for more details.
EBU-2688 Unable to find a Backup for db_name database in catalog
Cause: | Database name not specified correctly. | |
Refer to EBU Administrator's Guide for more details.
EBU-2689 Catalog database has not been upgraded to version number. Please run upgrade script
Cause: | Catalog database version out of date. | |
Refer to EBU Administrator's Guide for more details.
EBU-2690 Version number requires catalog version number. Current catalog version is number. Use newer code
Cause: | Catalog database version out of date. | |
Refer to EBU Administrator's Guide for more details.
EBU-2802 Target database information is out of date and -test was specified. Job will not be executed.
Cause: | Test run was to run against out of date target database information registered in catalog database. | |
Refer to EBU Administrator's Guide for more details.
EBU-2806 Target database information not found in catalog, proceeding to register
None
EBU-2807 Additional Database information:
None
EBU-2810 Name of database connected is db_name, and not db_name
Cause: | Database is not specified correctly. | |
Refer to EBU Administrator's Guide for more details.
EBU-2811 ORACLE_HOME directory_name must be a valid directory
Cause: | ORACLE_HOME directory is not specified correctly. | |
Refer to EBU Administrator's Guide for more details.
EBU-2813 Domain = domain_name
None
EBU-2815 Block size = number bytes
None
EBU-2816 Database created string
None
EBU-2817 Error while creating temporary database information in catalog database
Cause: | An Oracle error occurred. | |
Action: | Fix it before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2818 Error while creating temporary catalog information in catalog database
Cause: | An Oracle error occurred. | |
Action: | Fix it before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2819 Error while comparing catalog and current information in catalog database
Cause: | An Oracle error occurred. | |
Action: | Fix it before retrying. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2820 No registration update is needed, target database information is up to date
None
EBU-2823 Target database information was found to be out of date, registration update will take place
None
EBU-2824 Verifying registration information...
None
EBU-2825 Files registered in catalog are:
None
EBU-2826 Current database files are:
None
EBU-2827 Target database has been recreated
None
EBU-2828 Resetlogs operation has been performed on target database
None
EBU-2829 Error while reading target database login information
Action: | File a bug report. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-2830 Target database has changed ORACLE_HOME
None
EBU-3000 Error while executing fork system call
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-3001 Error while executing dup2 system call for <stdin>
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-3002 Error while executing dup2 system call for <stdout>
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-3003 Error while executing execve system call for string
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.
EBU-3004 Error while executing execv system call for string
Cause: | An error was returned by system call. | |
Action: | Report with runtime operating system configuration. | |
Backup Utility Vendor Support with the log file for the operation.