Oracle database error messages/8
From Just Solve the File Format Problem
(Difference between revisions)
(Changed category) |
Dan Tobias (Talk | contribs) |
||
Line 5,175: | Line 5,175: | ||
| Performing export of metadata... | | Performing export of metadata... | ||
|} | |} | ||
+ | [[Category:Oracle]] |
Latest revision as of 00:50, 21 August 2019
Please see Oracle database error message
Code | Message |
---|---|
KUP-04080 | directory object string not found |
KUP-04081 | field string used in concatenation for column string is not a character type |
KUP-04082 | error converting field string for LOBFILE column string |
KUP-04083 | no directory object specified in LOBFILE clause for column string |
KUP-04084 | The ORACLE_DATAPUMP access driver does not support the ROWID column. |
KUP-04085 | duplicate directory object string and file string specified for unload |
KUP-04086 | length of file name exceeds platform maximum of number |
KUP-04087 | no execute access to directory object string |
KUP-04088 | data sampling is not supported by this access driver |
KUP-04089 | column transform string is not the name of a table column |
KUP-04090 | big endian byte order mark found when little endian expected in string |
KUP-04091 | little endian byte order mark found when big endian expected in string |
KUP-04092 | attempt to audit directory object string returned internal error number |
KUP-04094 | preprocessing cannot be performed if Database Vault is installed |
KUP-04095 | preprocessor command string encountered error "string" |
KUP-04097 | RECORDS clause specified without a record format |
KUP-04100 | record rejected in file string |
KUP-04101 | record number rejected in file string |
KUP-04102 | record number discarded from file string |
KUP-04103 | error converting zoned decimal field to number for string |
KUP-04104 | zoned decimal field has bad values for string |
KUP-04105 | zoned decimal to number conversion caused overflow for string |
KUP-04106 | precision for zoned decimal number is too large for string |
KUP-04108 | unable to reread file string |
KUP-04109 | specified path for directory object "string" is invalid |
KUP-05004 | Warning: Intra source concurrency disabled because parallel select was not requested. |
KUP-05005 | Warning: Intra source concurrency disabled because a field of type RECNUM exists. |
KUP-05006 | Warning: Intra source concurrency disabled because a complex terminator string is being used. |
KUP-05007 | Warning: Intra source concurrency disabled because the preprocessor option is being used. |
KUP-05008 | Warning: Intra source concurrency disabled because the input data is in DELIMITED record format and the characterset is neither fixed width nor UTF8. |
KUP-05009 | Warning: Intra source concurrency disabled because the input data is in VARIABLE record format. |
KUP-11000 | file truncated error |
KUP-11001 | files not from the same unload operation |
KUP-11002 | unable to read data chunk string |
KUP-11003 | bad data encountered while reading from file string |
KUP-11004 | requested version string not supported by ORACLE_DATAPUMP |
KUP-11005 | error seeking in file: string |
KUP-11006 | file truncated error in string |
KUP-11007 | conversion error loading table string.string |
KUP-11008 | conversion error loading table string.string partition string |
KUP-11009 | data for row: string |
KUP-11010 | unable to open at least one dump file for fetch |
KUP-11011 | the following file is not valid for this load operation |
KUP-11012 | file string in string already exists |
KUP-11013 | internal number in header in file string is not valid |
KUP-11014 | internal metadata in file string is not valid |
KUP-11015 | error in unloading or loading data |
KUP-11016 | database version in file string is not valid |
KUP-11017 | file string not found |
KUP-11018 | file string not a valid dump file |
KUP-11019 | the following file is not valid for this fetch operation |
KUP-11020 | header in file string may not contain correct information |
KUP-11021 | header in file string has an incompatible version number |
KUP-11022 | specified file name "string" is invalid |
KUP-11023 | specified path for directory object "string" is invalid |
KUP-11024 | This external table can only be accessed from within a Data Pump job. |
UDE-00001 | user requested cancel of current operation |
UDE-00002 | invalid username or password |
UDE-00003 | all allowable logon attempts failed |
UDE-00004 | operation generated ORACLE error number |
UDE-00005 | unexpected End-Of-File encountered while reading input |
UDE-00006 | failed to allocate memory of size number |
UDE-00007 | attempt to free unallocated memory |
UDE-00010 | multiple job modes requested, string and string. |
UDE-00011 | parameter string is incompatible with parameter string |
UDE-00012 | table mode exports only allow objects from one schema |
UDE-00013 | internal expdp error. |
UDE-00014 | invalid value for parameter, 'string'. |
UDE-00015 | invalid context or job state for parameter, 'string'. |
UDE-00016 | 'string' parameter requires a value. |
UDE-00017 | Data Pump job is already executing. |
UDE-00018 | Data Pump client is incompatible with database version string |
UDE-00019 | 'string' parameter list is too long. |
UDE-00020 | Data Pump client is incompatible with Data Pump API. |
UDE-00050 | Unable to setup parameter processing. |
UDE-00051 | unable to set NLS_NUMERIC_CHARACTERS to required defaults. |
UDE-00052 | incorrect Data Pump client for operation: string |
UDE-00053 | unrecognized client command 'string' |
UDE-00054 | Deprecated Legacy Mode parameter 'string' specified at or on: string |
UDI-00001 | user requested cancel of current operation |
UDI-00002 | invalid username or password |
UDI-00003 | all allowable logon attempts failed |
UDI-00004 | operation generated ORACLE error number |
UDI-00005 | unexpected End-Of-File encountered while reading input. |
UDI-00006 | failed to allocate memory of size number |
UDI-00007 | attempt to free unallocated memory |
UDI-00010 | multiple job modes requested, string and string. |
UDI-00011 | parameter string is incompatible with parameter string |
UDI-00012 | table mode imports only allow objects from one schema |
UDI-00013 | internal impdp error. |
UDI-00014 | invalid value for parameter, 'string' |
UDI-00015 | invalid context or job state for parameter, 'string'. |
UDI-00016 | 'string' parameter requires a value. |
UDI-00017 | Data Pump job is already executing. |
UDI-00018 | Data Pump client is incompatible with database version string |
UDI-00019 | 'string' parameter list is too long. |
UDI-00020 | Data Pump client is incompatible with Data Pump API. |
UDI-00050 | unable to setup parameter processing. |
UDI-00051 | unable to set NLS_NUMERIC_CHARACTERS to required defaults. |
UDI-00052 | incorrect Data Pump client for operation: string |
UDI-00053 | unrecognized client command 'string' |
UDI-00054 | Deprecated Legacy Mode parameter 'string' specified at or on: string |
DBV-00200 | Block, DBA number, already marked corrupt |
DBV-00201 | Block, DBA number, marked corrupt for invalid redo application |
NID-00001 | Illegal command line syntax - parse error = (number) |
NID-00002 | Parse error: string |
NID-00010 | Password: |
NID-00100 | Cannot open datafile "string" |
NID-00101 | LOGFILE (string) not accessible |
NID-00102 | Garbled target string |
NID-00103 | Missing password in connect string "string" |
NID-00104 | Need to specify TARGET connection parameter in command line |
NID-00105 | Need to specify "LOGFILE=<logfile>" when using APPEND=YES option |
NID-00106 | LOGIN to target database failed with Oracle error: string |
NID-00107 | File I/O error on datafile "string" during string operation (number/string) |
NID-00109 | DBNAME string length number exceeds maximum length of number |
NID-00110 | Cannot use REVERT and specify a database name at the same time |
NID-00111 | Oracle error reported from target database while executing string string |
NID-00113 | Error reading answer - aborting |
NID-00114 | Must specify new database name when SETNAME is used |
NID-00115 | Database should be mounted |
NID-00120 | Database should be mounted exclusively |
NID-00121 | Database should not be open |
NID-00122 | Database should have no offline immediate datafiles |
NID-00123 | Magic number for datafile "string" is incorrect |
NID-00124 | Mismatched dbid for datafile string, expected number, found number |
NID-00125 | Database should have no disabled datafiles |
NID-00126 | Database should have no datafiles in unknown state |
NID-00127 | All online files in the database must have the same checkpoint SCN |
NID-00128 | Cannot revert change of database, change not in progress |
NID-00129 | Invalid DBID for datafile "string", expecting number, found number |
NID-00130 | Mismatched CHECKPOINT_CHANGE# in datafile "string", expecting string, found string |
NID-00131 | Control file is not current |
NID-00132 | CHECKPOINT_CHANGE# in datafile "string": string in the future of controlfile: string |
NID-00133 | Database should have only consistent datafiles |
NID-00134 | Datafile "string" is not consistent |
NID-00135 | There are number active threads |
NID-00137 | All datafiles that are not dropped should be readable |
NID-00138 | Block verification failed for datafile string (number) |
NID-00139 | Mismatched dbname for datafile string, expected string, found string |
NID-00140 | Specified database name string does not match previous name used string |
NID-00141 | No database name specified, previous attempt used string |
NID-00142 | Only changing database name, previous attempt changed dbid to number |
NID-00143 | Mismatched controlfile string |
NID-00144 | New name for database string is the same as current name string |
NID-00145 | nls subsystem initialization failure for product=string, facility=string |
NID-00300 | Connected to database string (DBID=number) |
NID-00301 | Datafile string - dbid changed, wrote new name |
NID-00302 | Datafile string - dbid changed |
NID-00303 | Datafile string - wrote new name |
NID-00304 | Datafile string - reverted |
NID-00305 | Datafile string - already changed |
NID-00306 | Datafile string - no revert needed |
NID-00307 | Control File string - dbid changed, wrote new name |
NID-00308 | Control File string - dbid changed |
NID-00309 | Control File string - wrote new name |
NID-00310 | Control File string - reverted |
NID-00311 | Control File string - modified |
NID-00312 | Connected to server version string |
NID-00315 | Operation already in progress, continuing |
NID-00320 | Operation cancelled at user request |
NID-00321 | Proceeding with operation |
NID-00330 | The following datafiles are offline immediate: |
NID-00331 | The following datafiles are disabled: |
NID-00332 | The following datafiles are in unknown state: |
NID-00333 | Cannot read the header of the following datafiles: |
NID-00334 | The following datafiles are not checkpointed to string: |
NID-00335 | The following datafiles are not consistent: |
NID-00336 | The following datafiles are offline clean: |
NID-00337 | The following datafiles are read-only: |
NID-00338 | Control Files in database: |
NID-00350 | string (number) string |
NID-00351 | string (number) |
NID-00352 | string (number), error: number |
NID-00353 | string |
NID-00354 | Instance shut down |
NID-00370 | Change database ID of database string? (Y/[N]) => |
NID-00371 | Change database name of database string to string? (Y/[N]) => |
NID-00372 | Change database ID and database name string to string? (Y/[N]) => |
NID-00373 | Revert changes for database string (Y/[N]) => |
NID-00390 | These files must be writable by this utility. |
NID-00395 | Reverting database name from string to string |
NID-00396 | Reverting database ID from number to number |
NID-00397 | Changing database name from string to string |
NID-00398 | Changing database ID from number to number |
NID-00400 | DBNEWID - Completed with errors. |
NID-00401 | Must finish REVERT changes before attempting any database operation. |
NID-00402 | Must finish change or REVERT changes before attempting any database operation. |
NID-00403 | DBNEWID - Completed with validation errors. |
NID-00404 | DBNEWID - Completed succesfully. |
NID-00405 | Reversion of database name and database ID failed. |
NID-00406 | Reversion of database name failed. |
NID-00407 | Reversion of database ID failed. |
NID-00410 | Reversion of database changes failed during validation - database is intact. |
NID-00415 | Change of database name and database ID failed. |
NID-00416 | Change of database name failed. |
NID-00417 | Change of database ID failed. |
NID-00420 | Change of database name and ID failed during validation - database is intact. |
NID-00421 | Change of database name failed during validation - database is intact. |
NID-00422 | Change of database ID failed during validation - database is intact. |
NID-00425 | Database name restored to string. |
NID-00426 | Database ID for database string restored to number. |
NID-00430 | Database is ready to be open or shut down. |
NID-00431 | DBNEWID - Reversion completed. |
NID-00435 | Database name changed to string. |
NID-00436 | Modify parameter file and generate a new password file before restarting. |
NID-00440 | Database ID for database string changed to number. |
NID-00441 | All previous backups and archived redo logs for this database are unusable. |
NID-00442 | Database has been shutdown, open database with RESETLOGS option. |
NID-00450 | Succesfully changed database name and ID. |
NID-00451 | Succesfully changed database name. |
NID-00452 | Succesfully changed database ID. |
NID-00480 | Database is intact - database is ready to be open or shut down. |
NID-00481 | DBNEWID - Cancelled. |
NID-00482 | Database is not aware of previous backups and archived logs in Recovery Area. |
NID-00490 | LOG being redirected to STDERR due to errors. |
NID-00500 | Keyword Description (Default) |
NID-00501 | ---------------------------------------------------- |
NID-00502 | TARGET Username/Password (NONE) |
NID-00503 | DBNAME New database name (NONE) |
NID-00504 | LOGFILE Output Log (NONE) |
NID-00505 | REVERT Revert failed change NO |
NID-00506 | SETNAME Set a new database name only NO |
NID-00507 | APPEND Append to output log NO |
NID-00508 | HELP Displays these messages NO |
NID-00600 | Internal Error - [number] [number] [number] [number] |
NID-00601 | Internal Error - [number] [string] [number] [number] |
NID-00602 | Could not allocate number bytes for "string" |
NID-00603 | No datafiles found in database |
NID-00604 | No control files found in database |
DGM-16900 | Unable to initialize client |
DGM-16901 | Unable to initialize environment |
DGM-16902 | Unable to allocate handle |
DGM-16903 | Unable to connect to database |
DGM-16904 | Unable to set attribute |
DGM-16905 | Failed. |
DGM-16906 | Unable to accept commands: no memory |
DGM-16909 | Fatal error - quitting... |
DGM-16910 | Unable to issue command to server |
DGM-16912 | Unrecognized command "string", try "help" |
DGM-16916 | Missing site name, try "help" |
DGM-16934 | start up instance "string" of database "string" |
DGM-16943 | connect to instance "string" of database "string" |
DGM-16944 | Failover succeeded, new primary is "string" |
DGM-16945 | Syntax error before or at "string" |
DGM-16946 | Site "string" was not found |
DGM-16948 | Unable to switchover, primary database is still "string" |
DGM-16949 | Object "string" was not found |
DGM-16951 | Unable to failover |
DGM-16952 | Configuration details cannot be determined by DGMGRL |
DGM-16953 | XML document is too long |
DGM-16954 | Unable to open and lock the Observer configuration file |
DGM-16959 | No response from broker server process |
DGM-16960 | Status not available |
DGM-16979 | Unable to log on to the primary or standby database as SYSDBA |
DGM-16991 | Two or more resources have the name "string" |
DGM-16999 | Instance "string" was not found |
DGM-17000 | Two or more instances have the name "string" |
DGM-17002 | Primary database cannot be removed |
DGM-17007 | Unsupported platform, observer cannot start |
DGM-17009 | New primary database "string" is opening... |
DGM-17016 | failed to retrieve status for database "string" |
DGM-17017 | unable to determine configuration status |
DIA-48001 | internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string] |
DIA-48002 | thread terminated by fatal error |
DIA-48003 | out of process memory when trying to allocate string bytes (string,string) |
DIA-48004 | unable to allocate string bytes of shared memory ("string","string","string","string") |
DIA-48007 | name is already used by an existing product type |
DIA-48008 | id is already used by an existing product type |
DIA-48100 | error encountered when attempting to open a file |
DIA-48101 | error encountered when attempting to read a file [string] [string] [string] |
DIA-48102 | encountered the end-of-file when reading the file |
DIA-48103 | error encountered when attempting to write a file [string] [string] [string] |
DIA-48104 | read mismatch on blocks requested and returned, [string], [string] |
DIA-48105 | write mismatch on blocks requested and returned, [string], [string] |
DIA-48106 | error initializing the ADR string object |
DIA-48107 | invalid Bfile input, [string] |
DIA-48108 | invalid value given for the diagnostic_dest init.ora parameter |
DIA-48109 | invalid lock mode for file descriptor, [string] |
DIA-48110 | error encountered while attempting to get a file lock [string] [string] |
DIA-48111 | error encountered while attempting to release a file lock [string] |
DIA-48112 | invalid flags for open file, string |
DIA-48113 | unable to write to stream file because of out of space condition |
DIA-48114 | error encountered when attempting to close a file |
DIA-48115 | error encountered while seeking a file position |
DIA-48116 | error enountered when attempting to create a directory [string] |
DIA-48117 | error encountered when attempting to remove a directory [string] |
DIA-48118 | error encountered with list directory [string] |
DIA-48119 | error encountered when attempting to remove a file [string] [string] |
DIA-48120 | error encountered when attempting to retrieve the file size [string] [string] |
DIA-48121 | error with opening the ADR stream file [string] [string] |
DIA-48122 | error with opening the ADR block file [string] [string] |
DIA-48123 | error encountered when attempting to flush a file |
DIA-48124 | device full encountered during write to a file |
DIA-48125 | illegal identifier length, argn:string, len:string, lim:string |
DIA-48126 | attempting to create a file that already exists |
DIA-48127 | attempting to open a file that does not exist |
DIA-48128 | opening of a symbolic link is disallowed |
DIA-48129 | invalid input for the full path specification |
DIA-48130 | invalid lock parameters for get file lock [string] |
DIA-48131 | error encountered when attempting to tell the file position |
DIA-48132 | requested file lock is busy, [string] [string] |
DIA-48133 | file descriptor has already been opened [string] [string] |
DIA-48134 | invalid file descriptor state for operation, string, string, string |
DIA-48135 | uninitialized file descriptor |
DIA-48136 | directory already exists [string] |
DIA-48137 | uninitialized file handle |
DIA-48138 | invalid directory name input for client address |
DIA-48139 | invalid input to ADR initialization routine |
DIA-48140 | the specified ADR Base directory does not exist [string] |
DIA-48141 | error creating directory during ADR initialization [string] |
DIA-48142 | invalid permissions input for change permissions |
DIA-48143 | error changing permissions for a file |
DIA-48144 | error encounted while performing standard file I/O |
DIA-48145 | invalid seek location, [string], [string] |
DIA-48146 | missing read, write, or exec permission on directory during ADR initialization [string] [string] |
DIA-48147 | invalid home location specification for ADR, [string], [string], [string] |
DIA-48148 | error encountered when attempting to move a file |
DIA-48149 | error encountered when attempting to copy a file |
DIA-48150 | error encountered with set current working directory |
DIA-48151 | error getting operating system time for a file |
DIA-48152 | lock table is full |
DIA-48153 | error encountered when getting ADR base directory default |
DIA-48154 | reached end of file for alert log |
DIA-48155 | error encountered when read alert log [string] |
DIA-48156 | Alert log purge has occurred - retry operation |
DIA-48157 | null input to ADR initialization |
DIA-48158 | invalid input for ADR base directory |
DIA-48159 | invalid input for ADR product type |
DIA-48160 | invalid input for ADR product id |
DIA-48161 | invalid input for ADR instance id |
DIA-48162 | string buffer too small to hold input, [string], [string], [string] |
DIA-48163 | error concatenating directory onto path, [string], [string], [string] |
DIA-48164 | error concatenating file onto path, [string], [string], [string] |
DIA-48165 | user missing read, write, or exec permission on specified ADR Base directory [string] |
DIA-48166 | error with opening ADR block file because file does not exist [string] [string] |
DIA-48167 | invalid argument for checking ADR initialization |
DIA-48168 | the ADR sub-system is not initialized |
DIA-48169 | incorrect arguments to ADR deferred initialization |
DIA-48170 | unable to lock file - already in use |
DIA-48171 | unable to get share lock - file not readable |
DIA-48172 | unable to find a valid ADR base |
DIA-48173 | error checking directory existence during ADR initialization [string] |
DIA-48174 | error encountered with get current working directory |
DIA-48175 | the path name must not contain the string '..'. |
DIA-48176 | error translating a path name into its full path name |
DIA-48177 | file name with full path information [string] not allowed |
DIA-48178 | error encountered while reading an ADR block file during ADR initialization [string] |
DIA-48179 | OS file synchronization failure |
DIA-48180 | OS open system call failure |
DIA-48181 | OS write system call failure |
DIA-48182 | OS read system call failure |
DIA-48183 | OS close system call failure |
DIA-48184 | OS seek system call failure |
DIA-48185 | OS file size system call failure |
DIA-48186 | OS check file exists system call failure |
DIA-48187 | specified directory does not exist |
DIA-48188 | user missing read, write, or exec permission on specified directory |
DIA-48189 | OS command to create directory failed |
DIA-48190 | OS unlink system call failure |
DIA-48191 | user missing read or write permission on specified file |
DIA-48192 | OS command to move a file failed |
DIA-48193 | OS command to open a directory failed |
DIA-48194 | OS command to close a directory failed |
DIA-48195 | OS command to remove a directory failed |
DIA-48196 | OS command to release advisory lock failed |
DIA-48197 | OS command to get the file status failed |
DIA-48198 | OS command to change the file permissions failed |
DIA-48199 | OS command to copy a file failed |
DIA-48200 | Illegal Input Argument [string] |
DIA-48201 | Field Length Exceeds Maximum [string] [string] [string] |
DIA-48202 | Illegal Identifier [string] [string] |
DIA-48203 | Illegal Data Type [string] |
DIA-48204 | Illegal Identifier Length [string] [string] [string] |
DIA-48205 | Record Length too Big [string] [string] [string] |
DIA-48206 | Ilegal Number of Fields [string] [string] [string] |
DIA-48207 | Illegal Field Name [string] |
DIA-48208 | Duplicate Field Names [string] |
DIA-48209 | Relation Already Exists |
DIA-48210 | Relation Not Found |
DIA-48211 | Illegal Access Mode [string] [string] |
DIA-48212 | Open Record Access Not Done |
DIA-48213 | Incorrect Access Mode for Operation [string] [string] |
DIA-48214 | Sequence Overflow [string] [string] [string] |
DIA-48215 | Sequence Invalid Operation [string] [string] |
DIA-48216 | Field Len Exceeds Max Field Length [string] [string] [string] [string] |
DIA-48217 | Out of Space on Device |
DIA-48218 | Duplicate Key Name [string] [string] |
DIA-48219 | Key Name Doesn't Match Any Existing Key |
DIA-48220 | Too Many Keys Defined [string] [string] |
DIA-48221 | Key Exceeds Maximum Allowed Length [string] [string] [string] |
DIA-48222 | Predicates/Order By Not Allowed |
DIA-48223 | Interrupt Requested - Fetch Aborted - Return Code [string] [string] |
DIA-48224 | DDL has occurred since parse - reparse [string] [string] [string] |
DIA-48225 | No More Space in Order By Buffer |
DIA-48226 | No Fetch in Progress |
DIA-48227 | Invalid Relation File - [string] [string] [string] [string] |
DIA-48228 | Missing Define Call [string] |
DIA-48229 | Invalid Relation Handle Provided [string] [string] |
DIA-48230 | Expression arguments must match types |
DIA-48231 | Predicate syntax error |
DIA-48232 | Debug command syntax error [string] |
DIA-48233 | Invalid Field Handle [string] [string] [string] |
DIA-48238 | Invalid Surrogate Length Specified [string] [string] |
DIA-48239 | Invalid Predicate Handle Provided [string] [string] |
DIA-48240 | Field is NOT NULL but NULL value supplied |
DIA-48242 | Fields that are NOT NULL can not use surrogates |
DIA-48243 | Additional Fields must be declared nulls allowed |
DIA-48244 | Purge for Retention can't be called while in an Query |
DIA-48245 | Attempt to Update/Delete when at EOF |
DIA-48246 | Illegal Operation on External Relation |
DIA-48247 | Predicate Conversion Error string |
DIA-48248 | Function string type check error; ityp = string typ = string arg = string |
DIA-48251 | Failed to open relation due to following error |
DIA-48252 | Relation does not require migration |
DIA-48258 | AMS Corrupt Page Found - Rebuild Relation |
DIA-48259 | AMS Relation not Created Correctly |
DIA-48260 | Function string not found |
DIA-48262 | Sequence references not allowed in predicates |
DIA-48263 | Currval not set yet - use nextval |
DIA-48265 | Incorrect number of arguments (string) provided - expected (string) |
DIA-48291 | Field name string can't be unique resolved |
DIA-48292 | Can't use outer join syntax mixed with inner join syntax |
DIA-48293 | Outer join syntax not allowed without a join |
DIA-48300 | Incident Record Already Exists |
DIA-48301 | An Invalid Incident ID was specified |
DIA-48302 | Incident Directory does not exist |
DIA-48303 | Exceeded max Incident Sequence Value |
DIA-48304 | incident staging file not found |
DIA-48305 | incident ID range is too large |
DIA-48309 | illegal incident state transition, [string] to [string] |
DIA-48310 | Incident string staging file not found |
DIA-48311 | Invalid field name [string] |
DIA-48312 | Sweep incident string staging file failed |
DIA-48313 | Updates not allowed on ADR relation [string] of Version=string |
DIA-48314 | Invalid ADR Control parameter [string] |
DIA-48315 | ADR unavailable |
DIA-48316 | relation [string] unavailable or cannot be created |
DIA-48317 | ADR Relation [string] of version=string is obsolete |
DIA-48318 | ADR Relation [string] of version=string cannot be supported |
DIA-48319 | Update operation on ADR relation [string] not allowed |
DIA-48320 | Too many incidents to report |
DIA-48321 | ADR Relation [string] not found |
DIA-48322 | Relation [string] of ADR V[string] incompatible with V[string] tool |
DIA-48323 | Specified pathname [string] must be inside current ADR home |
DIA-48324 | Incompatible staging file encountered |
DIA-48339 | view [string] does not exist |
DIA-48340 | operation not supported on view [string] |
DIA-48341 | Field [string] not a grouping field |
DIA-48342 | Field [string] cannot be mixed with string fields |
DIA-48343 | invalid field [string] reference in string clause |
DIA-48344 | Invalid Name [string] specified |
DIA-48345 | Timeout encountered during operation |
DIA-48400 | ADRCI initialization failed |
DIA-48401 | SET command requires arguments |
DIA-48402 | Variable is not defined |
DIA-48403 | DEFINE or UNDEFINE command has no arguments |
DIA-48404 | RUN or @ command has no arguments |
DIA-48405 | The option in the command is invalid |
DIA-48406 | ECHO or TERMOUT status must be set to ON or OFF |
DIA-48407 | DESCRIBE and QUERY commands need at least relation name argument |
DIA-48408 | The incident number exceeds the maximum number [string] |
DIA-48409 | The ADR homes exceeds the maximum number [string] |
DIA-48410 | The trace path exceeds the maximum number [string] |
DIA-48411 | The trace files exceeds the maximum number [string] |
DIA-48412 | The parameters exceeds the maximum number [string] |
DIA-48413 | The number of orderby fields exceeds maximum number [string] |
DIA-48414 | The string in the execution option exceeds maximum length [string] |
DIA-48415 | Syntax error found in string [string] at column [string] |
DIA-48419 | Illegal arguments |
DIA-48421 | Predicate string in the command must be single or double quoted |
DIA-48423 | IMPORT command must have a filename |
DIA-48424 | SHOW TRACE command needs argument |
DIA-48426 | The initialization filename is too long |
DIA-48428 | Input command string exceeds max length [string] |
DIA-48429 | Variable name [string] is an invalid identifier |
DIA-48431 | Must specify at least one ADR home path |
DIA-48432 | The ADR home path [string] is not valid |
DIA-48433 | Unknown help topic |
DIA-48434 | No DDE commands are input |
DIA-48435 | Input a trace file |
DIA-48436 | File [string] does not exist |
DIA-48437 | No IPS commands are input |
DIA-48438 | [string] is not a valid number |
DIA-48439 | The input path name exceeds the maximum length [string] |
DIA-48440 | Variable [string] is already defined |
DIA-48441 | The function parameter number exceeds the maximum number [string] |
DIA-48442 | The control parameter number exceeds the maximum number [string] |
DIA-48443 | Trace Record type appears in the middle of the path |
DIA-48444 | The single "." and "*" cannot appear in the middle of the path |
DIA-48445 | Path expression only supports one bucket dump type |
DIA-48446 | The command needs path input |
DIA-48447 | The input path [string] does not contain any ADR homes |
DIA-48448 | This command does not support multiple ADR homes |
DIA-48449 | Tail alert can only apply to single ADR home |
DIA-48457 | ADRCI core dumped |
DIA-48458 | "show incident" failed due to the following errors |
DIA-48459 | "describe" command only supports one ADR home path |
DIA-48460 | The home path [string] is not valid |
DIA-48461 | "describe" failed due to the following errors |
DIA-48462 | Fatal error encountered in [string] |
DIA-48463 | The value buffer reached the maximum length [string] |
DIA-48464 | The predicate buffer reached the maximum length [string] |
DIA-48465 | The specified type [string] is undefined |
DIA-48466 | Internal failure, the report context is not initialized |
DIA-48467 | "string" for the keyword "string" is not a valid number |
DIA-48468 | "string" is not a valid keyword |
DIA-48469 | Keyword "string" cannot be duplicated |
DIA-48470 | Unknown "string" command |
DIA-48472 | Invalid product name |
DIA-48473 | Internal failure, unknown return code [string] |
DIA-48474 | Syntax error specifying product, must not be NULL |
DIA-48475 | [string] is not a valid timestamp |
DIA-48476 | Cannot write the results out to a file, please check if the environment variable TMPDIR is set or the current directory is not writable |
DIA-48477 | The input path does not contain any valid ADR homes |
DIA-48478 | No alert messages are created |
DIA-48479 | No HM runs are created |
DIA-48480 | No incidents are created |
DIA-48481 | Report is not available |
DIA-48482 | Report is not generated |
DIA-48483 | Spooling failed, it may be because the spool file cannot be created due to a permission issue |
DIA-48484 | Run script failed, it may be because the script file does not exist |
DIA-48485 | The file exceeds the maximum length [string] |
DIA-48486 | The file [string] exceeds the maximum length [string] |
DIA-48487 | The internal predicate string exceeds the maximum length [string] |
DIA-48488 | The predicate string exceeds the maximum length [string] |
DIA-48489 | The input exceeds the maximum length [string] |
DIA-48490 | The field number exceeds the maximum number [string] |
DIA-48491 | The program name is too long, exceeds the maximum length [string] |
DIA-48492 | The report component name is not defined |
DIA-48493 | Sweep command needs parameters |
DIA-48494 | ADR home is not set, the corresponding operation cannot be done |
DIA-48495 | Interrupt requested |
DIA-48496 | "string" is a mandatory keyword for the command |
DIA-48497 | "string" is an invalid product type |
DIA-48499 | The value of the keyword "string" exceeds the maximum length string |
DIA-48500 | File Write Error [string] [string] |
DIA-48501 | File Read Error [string] [string] |
DIA-48502 | Invalid Command Line - Missing Required Elements |
DIA-48503 | Invalid Parameter Specified |
DIA-48504 | Relation Parameter Must be Specified |
DIA-48505 | File Parameter Must be Specified |
DIA-48506 | Existing Relation at different version than export [string] [string] |
DIA-48507 | Predicate Not Allowed during Import |
DIA-48508 | Export File Version [string] Can Not be Used by Import [string] |
DIA-48509 | Error occurred during operation. See the following errors |
DIA-48510 | Can not export an in memory relation |
DIA-48600 | HM run with name [string] already exists |
DIA-48615 | Parameter [string] value not specified |
DIA-48800 | "string" for the keyword "string" is not in the right format of timestamp |
DIA-48801 | The option "string" is duplicated |
DIA-48802 | The options "string" and "string" are mutual exclusive |
DIA-48803 | The keyword "string" is not defined for this command |
DIA-48804 | The command needs at least one file input |
DIA-48805 | BEGIN BACKUP issued already - must do an END BACKUP first |
DIA-48806 | Unknown Function Reference (string) |
DIA-48900 | Illegal Input Argument [string] |
DIA-48906 | Parser context is not valid |
DIA-48907 | The end of file is reached |
DIA-48908 | No trace files are found |
DIA-48909 | Scan context is not initialized |
DIA-48912 | The specified trace filename is too long |
DIA-48913 | Writing into trace file failed, file size limit [string] reached |
DIA-48914 | File position is not in right format |
DIA-48928 | The predicate exceeds the max limit string |
DIA-48929 | The trace record size exceeded the max size that can be read [string] |
DIA-48930 | Cannot allocate memory for processing traces |
DIA-48934 | invalid input for the file name identifier |
DIA-48936 | The number of relations exceeds maximum number [string] |
DIA-48937 | Feature (string) currently not allowed for SELECT |
DIA-48938 | View select column count differs from select alias list |
DIA-48939 | Select * not allowed in a CREATE VIEW |
DIA-49315 | Invalid incident type specified [string] |
DIA-49404 | No such package [string] |
DIA-49405 | Cannot change package name [string] [string] |
DIA-49406 | Undefined configuration parameter specified [string] |
DIA-49407 | No unpacking history in this home |
DIA-49408 | Invalid home specified [string] |
DIA-49409 | Incremental package provided when complete expected |
DIA-49410 | Not an IPS package |
DIA-49412 | Package ID does not match existing ID [string] [string] |
DIA-49413 | Package name does not match existing name [string] [string] |
DIA-49414 | Package sequence later than expected [string] [string] |
DIA-49415 | Package sequence earlier than expected [string] [string] |
DIA-49416 | Earlier package sequence applied with FORCE option [string] [string] |
DIA-49417 | Cannot modify already generated package |
DIA-49420 | Package too large [string] [string] |
DIA-49421 | Maximum number of package files generated [string] |
DIA-49423 | File outside ADR not allowed |
DIA-49424 | Directory outside ADR not allowed |
DIA-49425 | File inside ADR not allowed |
DIA-49426 | Directory inside ADR not allowed |
DIA-49427 | No such file or file not accessible [string] |
DIA-49428 | No such directory or directory not accessible [string] |
DIA-49429 | File already exists and OVERWRITE option not specified [string] |
DIA-49430 | No such problem [string] |
DIA-49431 | No such incident [string] |
DIA-49432 | Problem not part of package [string] |
DIA-49433 | Incident not part of package [string] |
DIA-49434 | Invalid date format |
DIA-49435 | Flood-controlled incident not allowed here [string] |
DIA-49436 | Date conversion error [string] |
DIA-49440 | Warnings while unpacking package, details in file string |
DIA-49441 | Warnings while finalizing package, details in file string |
DIA-49450 | Non-zero return code from archiving utility [string] [string] |
DIA-49451 | Archive file structure error [string] [string] |
DIA-49452 | Archiving utility out of memory [string] [string] |
DIA-49453 | Invalid command invoking archiving utility [string] [string] |
DIA-49454 | Archive is missing or empty [string] [string] |
DIA-49455 | Archive I/O failed [string] [string] |
DIA-49456 | Operation failed due to insufficient disk space [string] [string] |
DIA-49601 | syntax error: found "string": expecting one of: "string" etc.. |
DIA-51001 | check [string] not found in HM catalog |
DIA-51003 | run parameters not formatted correctly |
DIA-51004 | Check doesn't take any input params |
DIA-51006 | unexpected delimter ';' in the run params text |
DIA-51007 | parameter [string] not registered with this check |
DIA-51008 | parameter [string] value is not a proper number |
DIA-51025 | check name should be non NULL value |
DIA-51035 | invalid timeout value |
DIA-51036 | check [string] can only be executed in database instance |
DIA-51037 | check [string] can only be executed in ASM instance |
DIA-51102 | cannot change priority of a critical failure string |
DIA-51103 | cannot change priority of a closed failure string |
DIA-51105 | cannot change priority of a failure to CRITICAL |
DIA-51106 | check failed to complete due to an error. See error below |
DIA-51107 | failures are changing too rapidly - retry command |
DIA-51108 | unable to access diagnostic repository - retry command |
DIA-51109 | repair script file is too large |
DIA-51110 | buffer size [string] is too small - [string] is needed |
DIA-51111 | failure revalidation timed out |
DIA-51190 | Internal error [string], [string] from DBMS_IR |
DIA-51191 | Too many files opened |
DIA-51192 | File not open |
DIA-51193 | invalid parameter value |
DIA-51303 | illegal check mask value specified |
DIA-51316 | No check meta-data found on specified table string |
DIA-51700 | Invalid file URL |
DIA-51701 | Invalid file URL or path prefix |
DIA-51702 | Could not find file at URL provided |
DIA-51703 | Missing <body> tag from HTML |
DIA-51704 | Error string received from XPath engine |
DIA-51705 | XML string error: string "string" |
LCD-00100 | internal error, argument [number] |
LCD-00111 | value not in legal range [string] |
LCD-00112 | illegal integer radix specification [string] |
LCD-00113 | integer conversion error or negative integer [string] |
LCD-00114 | illegal boolean response [string] |
LCD-00122 | unrecognized keyword [string] |
LCD-00128 | invalid positional parameter value [string] |
LCD-00161 | ORACLE error (possible syntax error) parameter [string] |
LCD-00201 | could not open specified filename [string] |
LCD-00203 | missing keyword [string] |
LCD-00204 | left parenth and no parameter specified [string] |
LCD-00205 | unbalanced parentheses [string] |
LCD-00206 | positional parameter entered after keyword [string] |
LCD-00207 | nested parentheses encountered [string] |
LCD-00208 | unexpected keyword in value list [string] |
LCD-00209 | missing value for keyword at end of string [string] |
LCD-00210 | illegal assignment operator [string] |
LCD-00211 | unexpected delimiter [string] |
LCD-00212 | runaway quoted string [string] |
LCD-00215 | parameter files nested too deep [string] |
LCD-00217 | failure while processing file parameter [string] |
LCD-00218 | error in file [string] |
LCD-00219 | nested include file [string] is too large |
OCI-00601 | cleanup lock conflict |
OCI-00602 | internal programming exception |
OCI-00972 | identifier is too long |
OCI-01841 | (full) year must be between -4713 and +9999, and not be 0 |
OCI-01854 | julian date must be between 1 and 5373484 |
OCI-01858 | a non-numeric character was found where a numeric was expected |
OCI-01859 | a non-alphabetic character was found where an alphabetic was expected |
OCI-01861 | literal does not match format string |
OCI-01862 | wrong number of digits for this format item |
OCI-01864 | the date is out of range for the current calendar |
OCI-01865 | not a valid era |
OCI-01867 | the interval was invalid |
OCI-01868 | the leading precision of the interval was too small |
OCI-01870 | the intervals or datetimes were not mutually comparable |
OCI-01871 | the number of seconds must be less than 60 |
OCI-01873 | the leading precision of the interval was too small |
OCI-01874 | time zone hour must be between -12 and 14 |
OCI-01875 | time zone minute must be between -59 and 59 |
OCI-01876 | year must be at least -4713 |
OCI-01878 | specified field not found in datetime or interval |
OCI-01879 | the hh25 field must be between 0 and 24 |
OCI-01880 | the fractional seconds must be between 0 and 999999999 |
OCI-01881 | time zone region ID is invalid |
OCI-01882 | time zone region not found |
OCI-01883 | overlap was disabled during a region transition |
OCI-01884 | divisor is equal to zero |
OCI-01890 | NLS error detected |
OCI-01898 | too many precision specifiers |
OCI-02083 | database name has illegal character 'string' |
OCI-02084 | database name is missing a component |
OCI-04020 | deadlock detected while trying to lock object stringstringstringstringstring |
OCI-04021 | timeout occurred while waiting to lock object stringstringstringstringstring |
OCI-04022 | nowait requested, but had to wait to lock dictionary object |
OCI-04028 | cannot generate diana for object stringstringstringstringstring |
OCI-04029 | error ORA-string occurred when querying stringstringstring |
OCI-04030 | out of process memory when trying to allocate string bytes (string,string) |
OCI-04031 | unable to allocate string bytes of shared memory ("string","string","string") |
OCI-04054 | database link string does not exist |
OCI-04060 | insufficient privileges to execute string |
OCI-04061 | existing state of string has been invalidated |
OCI-04062 | timestamp of string has been changed |
OCI-04063 | string has errors |
OCI-04064 | not executed, invalidated string |
OCI-04065 | not executed, altered or dropped string |
OCI-04066 | non-executable object, string |
OCI-04067 | not executed, string does not exist |
OCI-04068 | existing state of packagesstringstringstring has been discarded |
OCI-19200 | Invalid column specification |
OCI-19201 | Datatype not supported |
OCI-19202 | Error occurred in XML processingstring |
OCI-19203 | Error occurred in DBMS_XMLGEN processingstring |
OCI-19204 | Non-scalar value 'string' is marked as XML attribute |
OCI-19205 | Attribute 'string' qualifies a non-scalar value in the select list |
OCI-19206 | Invalid value for query or REF CURSOR parameter |
OCI-19207 | scalar parameter string of XMLELEMENT cannot have an alias. |
OCI-19208 | parameter string of function string must be aliased |
OCI-19209 | invalid or unsupported formatting argument |
OCI-19210 | column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string' |
OCI-19211 | column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type |
OCI-19212 | no key columns specified before call to DBMS_XMLSTORE.updateXML() |
OCI-21300 | objects option not installed |
OCI-21301 | not initialized in object mode |
OCI-21500 | internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string] |
OCI-21501 | program could not allocate memory |
OCI-21503 | program terminated by fatal error |
OCI-21520 | database server driver not installed |
OCI-21521 | exceeded maximum number of connections in OCI (object mode only) |
OCI-21522 | attempted to use an invalid connection in OCI (object mode only) |
OCI-21523 | functionality not supported by the server (object mode only) |
OCI-21524 | object type mismatch |
OCI-21525 | attribute number (or collection element at index) string violated its constraints |
OCI-21526 | initialization failed |
OCI-21527 | internal OMS driver error |
OCI-21560 | argument string is null, invalid, or out of range |
OCI-21562 | column string has unsupported data type string |
OCI-21563 | Error string while calling string for column string with datatype string |
OCI-21570 | current string LCR has unreceived chunk data |
OCI-21571 | must provide a LOB WRITE, LOB TRIM or LOB ERASE LCR in string call (input LCR=string) |
OCI-21572 | Invalid LCR type (string) in string call |
OCI-21573 | Invalid command type (string) when sending a chunk. |
OCI-21574 | Invalid data type (string) specified for LOB chunk. |
OCI-21577 | Input string LCR has no LOB column. |
OCI-21578 | Only one LOB column allowed per string LCR. |
OCI-21579 | Input LCR must have at least one old or new column. |
OCI-21580 | The LOB operation length (value=string) for column (string) must be an even number of bytes. |
OCI-21583 | invalid XStream server name 'string' |
OCI-21600 | path expression too long |
OCI-21601 | attribute is not an object |
OCI-21602 | operation does not support the specified typecode |
OCI-21603 | property id [string] is invalid |
OCI-21604 | property [string] is not a property of transient or value instances |
OCI-21605 | property [string] is not a property of value instances |
OCI-21606 | can not free this object |
OCI-21607 | memory cartridge service handle not initialized |
OCI-21608 | duration is invalid for this function |
OCI-21609 | memory being resized without being allocated first |
OCI-21610 | size [string] is invalid |
OCI-21611 | key length [string] is invalid |
OCI-21612 | key is already being used |
OCI-21613 | key does not exist |
OCI-21700 | object does not exist or is marked for delete |
OCI-21701 | attempt to flush objects to different servers |
OCI-21702 | object is not instantiated or has been de-instantiated in cache |
OCI-21703 | cannot flush an object that is not modified |
OCI-21704 | cannot terminate cache or connection without flushing first |
OCI-21705 | service context is invalid |
OCI-21706 | duration does not exist or is invalid |
OCI-21707 | pin duration is longer than allocation duration |
OCI-21708 | inappropriate operation on a transient object |
OCI-21709 | cannot refresh an object that has been modified |
OCI-21710 | argument is expecting a valid memory address of an object |
OCI-21779 | duration not active |
OCI-22053 | overflow error |
OCI-22054 | underflow error |
OCI-22055 | unknown sign flag value [string] |
OCI-22056 | value [string] is divided by zero |
OCI-22057 | bad integer length [string] |
OCI-22059 | buffer size [string] is too small - [string] is needed |
OCI-22060 | argument [string] is an invalid or uninitialized number |
OCI-22061 | invalid format text [string] |
OCI-22062 | invalid input string [string] |
OCI-22063 | reading negative value [string] as unsigned |
OCI-22064 | invalid NLS parameter string [string] |
OCI-22065 | number to text translation for the given format causes overflow |
OCI-22130 | buffer size [string] is less than the required size [string] |
OCI-22131 | hexadecimal string length is zero |
OCI-22132 | hexadecimal string does not correspond to a valid REF |
OCI-22140 | given size [string] must be in the range of 0 to [string] |
OCI-22141 | given size [string] must be even in UTF-16 environment |
OCI-22150 | variable-length array has not been initialized |
OCI-22151 | cannot resize non-zero variable-length array to zero elements |
OCI-22152 | destination variable-length array is not initialized |
OCI-22153 | source variable-length array is not initialized |
OCI-22160 | element at index [string] does not exist |
OCI-22161 | type code [string] is not valid |
OCI-22162 | element at index [string] has been previously deleted |
OCI-22163 | left hand and right hand side collections are not of same type |
OCI-22164 | delete element operation is not allowed for variable-length array |
OCI-22165 | given index [string] must be in the range of [string] to [string] |
OCI-22166 | collection is empty |
OCI-22167 | given trim size [string] must be less than or equal to [string] |
OCI-22275 | invalid LOB locator specified |
OCI-22276 | invalid locator for LOB buffering |
OCI-22277 | cannot use two different locators to modify the same LOB |
OCI-22278 | must update the LOB only through the LOB buffers |
OCI-22279 | cannot perform operation with LOB buffering enabled |
OCI-22280 | no more buffers available for operation |
OCI-22281 | cannot perform operation with an updated locator |
OCI-22282 | non-contiguous append to a buffering enabled LOB not allowed |
OCI-22285 | non-existent directory or file for string operation |
OCI-22286 | insufficient privileges on directory or file to perform string operation |
OCI-22287 | invalid or modified directory occurred during string operation |
OCI-22288 | file operation string failed string |
OCI-22289 | cannot perform string operation on an unopened file |
OCI-22290 | operation would exceed the maximum number of opened files |
OCI-22303 | type "string"."string" not found |
OCI-22305 | attribute/method/parameter "string" not found |
OCI-22306 | type "string"."string" already exists |
OCI-22307 | type to alter is not a user-defined type |
OCI-22309 | attribute with name "string" already exists |
OCI-22311 | type for attribute "string" does not exist |
OCI-22313 | cannot use two versions of the same type "string" |
OCI-22314 | method information mismatch in ALTER TYPE |
OCI-22315 | type "string" does not contain a map or order function |
OCI-22316 | input type is not a collection type |
OCI-22317 | typecode number is not legal as a number type |
OCI-22318 | input type is not an array type |
OCI-22319 | type attribute information altered in ALTER TYPE |
OCI-22321 | method does not return any result |
OCI-22337 | the type of accessed object has been evolved |
OCI-22369 | invalid parameter encountered in method string |
OCI-22370 | incorrect usage of method string |
OCI-22600 | encountered 8.0.2 (Beta) VARRAY data that cannot be processed |
OCI-22601 | pickler TDS context [string] is not initialized |
OCI-22602 | pickler TDS handle [string] is not well-formed |
OCI-22603 | cannot add an attribute to the already generated TDS handle |
OCI-22604 | TDS handle already generated |
OCI-22605 | FDO handle [string] is not initialized |
OCI-22606 | pickler image handle [string] is not well-formed |
OCI-22607 | image handle already generated |
OCI-22608 | cannot add an attribute to the already generated image handle |
OCI-22609 | error string during initialization of FDO |
OCI-22626 | Type Mismatch while constructing or accessing OCIAnyData |
OCI-22975 | cannot create a PRIMARY KEY-based REF to this object view |
OCI-22976 | incorrect number of arguments to MAKE_REF |
OCI-30100 | internal error [number] |
OCI-30101 | unknown parameter name 'string' |
OCI-30102 | 'string' is not in the legal range for 'string' |
OCI-30103 | 'string' contains an illegal integer radix for 'string' |
OCI-30104 | 'string' is not a legal integer for 'string' |
OCI-30105 | 'string' is not a legal boolean for 'string' |
OCI-30107 | parameter name abbreviation 'string' is not unique |
OCI-30108 | invalid positional parameter value 'string' |
OCI-30109 | could not open parameter file 'string' |
OCI-30110 | syntax error at 'string' |
OCI-30111 | no closing quote for value 'string' |
OCI-30112 | multiple values not allowed for parameter 'string' |
OCI-30113 | error when processing file 'string' |
OCI-30114 | error when processing from command line |
OCI-30115 | error when processing an environment variable |
OCI-30116 | syntax error at 'string' following 'string' |
OCI-30117 | syntax error at 'string' at the start of input |
OCI-30118 | syntax error at 'string' at the end of input |
OCI-30119 | unable to obtain a valid value for 'string' |
OCI-30120 | 'string' is not a legal oracle number for 'string' |
OCI-30121 | 'string' is not an allowable value for 'string' |
OCI-30122 | value 'string' for 'string' must be between 'number' and 'number' |
OCI-30129 | invalid function argument received |
OCI-30130 | invalid parameter key type received |
OCI-30131 | number of keys being set exceeds allocation |
OCI-30132 | invalid key index supplied |
OCI-30135 | OCI Thread operation fails |
OCI-30150 | Invalid argument passed to OCIFile function |
OCI-30151 | File already exists |
OCI-30152 | File does not exist |
OCI-30153 | An invalid File Object is passed to the OCIFile function |
OCI-30154 | The memory address given as buffer for OCIFileRead/Write is invalid |
OCI-30155 | An I/O Error occured during an OCIFile function call |
OCI-30156 | Out of disk space |
OCI-30157 | An invalid argument was given to operating system call |
OCI-30158 | The OCIFileWrite causes the file to exceed the maximum allowed size |
OCI-30159 | OCIFileOpen: Cannot create the file or cannot open in the requested mode |
OCI-30160 | Unable to access the file |
OCI-30161 | A system error occurred during the OCIFile function call |
OCI-30162 | The OCIFile context is not initialzed |
OCI-30163 | The thread safety initialization failed |
OCI-30175 | invalid type given for an argument |
OCI-30176 | invalid format code used in the format string |
OCI-30177 | invalid flag used in a format specification |
OCI-30178 | duplicate flag used in a format specification |
OCI-30179 | invalid argument index used in a format code |
OCI-30180 | argument index is too large |
OCI-30181 | integer in argument index is not immediately followed by ) |
OCI-30182 | invalid precision specifier |
OCI-30183 | invalid field width specifier |
OCI-30184 | argument type not compatible with a format code |
OCI-30185 | output too large to fit in the buffer |
OCI-30191 | missing argument list |
OCI-30930 | XML node 'string' (type=string) does not support this operation |
OCI-30931 | Element 'string' cannot contain mixed text |
OCI-30932 | Reference node 'string' not contained in specified parent node 'string' |
OCI-30933 | Element 'string' may not appear at this point within parent 'string' |
OCI-30934 | 'string' (string node) cannot be inserted in parent 'string' (string node) |
OCI-30935 | XML maxoccurs value (string) exceeded |
OCI-30936 | Maximum number (string) of 'string' XML node elements exceeded |
OCI-30937 | No schema definition for 'string' (namespace 'string') in parent 'string' |
OCI-30938 | No prefix defined for namespace 'string' (particle string) |
OCI-30939 | Order violation: Element 'string' may not follow element 'string' |
OCI-30940 | Cannot resolve prefix 'string' for QName node 'string' |
OCI-30941 | Cannot specify empty URI for non-default namespace 'string' |
OCI-30942 | XML Schema Evolution error for schema 'string' table string column 'string' |
OCI-30943 | XML Schema 'string' is dependent on XML schema 'string' |
OCI-30944 | Error during rollback for XML schema 'string' table string column 'string' |
OCI-30945 | Could not create mapping table 'string' |
OCI-30946 | XML Schema Evolution warning: temporary tables not cleaned up |
OCI-30951 | Element or attribute at Xpath string exceeds maximum length |
OCI-30990 | insufficient privileges to change owner of resource string |
OCI-30991 | cannot use DOM to add special attribute to schema-based parent |
OCI-31000 | Resource 'string' is not an XDB schema document |
OCI-31001 | Invalid resource handle or path name "string" |
OCI-31002 | Path name string is not a container |
OCI-31003 | Parent string already contains child entry string |
OCI-31004 | Length string of the BLOB in XDB$H_INDEX is below the minimum string |
OCI-31005 | Path name length string exceeds maximum length string |
OCI-31006 | Path name segment length string exceeds maximum length string |
OCI-31007 | Attempted to delete non-empty container string/string |
OCI-31009 | Access denied for property string |
OCI-31010 | XML element index string exceeds maximum insertion index string |
OCI-31011 | XML parsing failed |
OCI-31012 | Given XPATH expression not supported |
OCI-31013 | Invalid XPATH expression |
OCI-31014 | Attempted to delete the root container |
OCI-31015 | Attempted to insert entry without name |
OCI-31016 | Attempted to delete entry without name |
OCI-31017 | Error generating unique OID for XML document |
OCI-31018 | Error deleting XML document |
OCI-31019 | Recursive deletion snapshot too old for string/string |
OCI-31020 | The operation is not allowed, Reason: string |
OCI-31021 | Element definition not found |
OCI-31022 | Element not found |
OCI-31023 | Index size error |
OCI-31025 | Invalid document element |
OCI-31027 | Path name or handle string does not point to a resource |
OCI-31028 | Resource metadata length string exceeded maximum length string |
OCI-31029 | Cannot bind to unsaved resource |
OCI-31030 | Unable to retrieve XML document |
OCI-31033 | Requested number of XML children string exceeds maximum string |
OCI-31035 | Could not bind locked resource to path string/string |
OCI-31037 | Invalid XML attribute name string |
OCI-31038 | Invalid string value: "string" |
OCI-31039 | XML namespace length string exceeds maximum string |
OCI-31040 | Property string: XML type (string) not compatible with internal memory type (string) |
OCI-31041 | Property string: Memory type (string) not compatible with database type (string) |
OCI-31042 | Too many properties in type 'string' |
OCI-31043 | Element 'string' not globally defined in schema 'string' |
OCI-31044 | Top-level prefix length string exceeds maximum string |
OCI-31045 | Cannot store more than string extras outside the root XML node |
OCI-31046 | Incorrect argument(s) specified in the operator |
OCI-31047 | Could not retrieve resource data at path string |
OCI-31048 | Unsaved resources cannot be updated |
OCI-31050 | Access denied |
OCI-31051 | Requested access privileges not supported |
OCI-31052 | Cannot delete ACL with other references |
OCI-31053 | The value of the depth argument in the operator cannot be negative |
OCI-31054 | The string operator cannot have an ancillary operator |
OCI-31055 | A null XMLType element cannot be inserted into RESOURCE_VIEW |
OCI-31056 | The document being inserted does not conform to string |
OCI-31057 | Display Name of the element being inserted is null |
OCI-31058 | cannot modify read-only XOBs |
OCI-31059 | Cannot insert root XML document node if it already exists |
OCI-31060 | Resource at path string could not be deleted |
OCI-31061 | XDB error: string |
OCI-31062 | Cannot delete an unsaved resource |
OCI-31065 | Cannot modify read-only property [string] |
OCI-31066 | Insertion of string into string creates a cycle |
OCI-31067 | XML nodes must be updated with nodes of the same type |
OCI-31068 | updateXML expected data format [string] instead of [string] |
OCI-31069 | Cannot apply typed changes to non-schema-based XMLType nodes |
OCI-31070 | Invalid database user ID string |
OCI-31071 | Invalid database username or GUID string |
OCI-31072 | Too many child nodes in XMLType fragment for updateXML |
OCI-31073 | Resource not retrieved using path name |
OCI-31075 | invalid string declaration in XML Schema |
OCI-31076 | required attribute "string" not specified |
OCI-31077 | invalid attribute "string" specified |
OCI-31078 | error in SQL mapping information |
OCI-31079 | unable to resolve reference to string "string" |
OCI-31080 | type not specified for attribute or element "string" |
OCI-31081 | name not specified for global declaration |
OCI-31082 | invalid attribute "string" specified in declaration of "string" |
OCI-31083 | error while creating SQL type "string"."string" |
OCI-31084 | error while creating table "string"."string" for element "string" |
OCI-31085 | schema "string" already registered |
OCI-31086 | insufficient privileges to register global schema "string" |
OCI-31087 | insufficient privileges to delete schema "string" |
OCI-31088 | object "string"."string" depends on the schema |
OCI-31089 | schema "string" does not target namespace "string" |
OCI-31090 | invalid database schema name "string" |
OCI-31091 | empty string specified as a SQL name |
OCI-31092 | invalid SQL name "string" |
OCI-31093 | null or invalid value specified for parameter : string |
OCI-31094 | incompatible SQL type "string" for attribute or element "string" |
OCI-31095 | cannot generate string : "string.string" already exists |
OCI-31096 | validation failed for schema |
OCI-31097 | Hierarchical Index not empty |
OCI-31099 | XDB Security Internal Error |
OCI-31100 | XDB Locking Internal Error |
OCI-31101 | Token "string" not given while locking resource "string" |
OCI-31102 | Already locked in exclusive mode. Cannot add lock. |
OCI-31103 | Resource locked in shared mode. Cannot add exclusive lock |
OCI-31104 | Cannot find lock with token "string" on "string" for unlock |
OCI-31105 | User does not own lock "string" |
OCI-31107 | Action failed as resource "string" is locked by name lock |
OCI-31108 | Action failed as resource string is locked |
OCI-31109 | Action failed as parent resource string is locked |
OCI-31110 | Action failed as resource string is locked by name |
OCI-31111 | table string cannot be hierarchically enabled |
OCI-31112 | fail to string for string port using xdb configuration |
OCI-31113 | XDB configuration may not be updated with non-schema compliant data |
OCI-31114 | XDB configuration has been deleted or is corrupted |
OCI-31115 | XDB configuration error: string |
OCI-31116 | Tablespace not specified correctly |
OCI-31121 | The string operator can not be FALSE |
OCI-31122 | The string operator has incorrect RHS value |
OCI-31151 | Cyclic definition encountered for string: "string" |
OCI-31153 | Cannot create schema URL with reserved prefix "http://xmlns.oracle.com/xdb/schemas/" |
OCI-31154 | invalid XML document |
OCI-31155 | attribute string not in XDB namespace |
OCI-31157 | Invalid Content-Type charset |
OCI-31158 | schema "string" currently being referenced |
OCI-31159 | XML DB is in an invalid state |
OCI-31160 | max substitution group size string exceeded by "string" (string) for head element "string" (string) |
OCI-31161 | element or attribute "string" cannot be stored out of line |
OCI-31162 | element or attribute "string" has no SQLType specified |
OCI-31163 | element or attribute "string" has invalid attribute value "string" (should be "string") |
OCI-31164 | cannot load object-relational XML attribute using direct path |
OCI-31165 | cannot load object-relational XML attribute using direct path |
OCI-31167 | XML nodes over 64K in size cannot be inserted |
OCI-31168 | Node localname and namespace values should be less than 64K |
OCI-31180 | DOM Type mismatch in invalid PL/SQL DOM handle |
OCI-31181 | PL/SQL DOM handle accesses node that is no longer available |
OCI-31182 | Too many PL/SQL DOM handles specified |
OCI-31185 | DOM Nodes do not belong to the same DOM Document |
OCI-31190 | Resource string is not a version-controlled resource |
OCI-31191 | Resource string is already checked out |
OCI-31192 | Resource string has not been checked out |
OCI-31193 | This versioning feature isn't supported for resource string |
OCI-31194 | Resource string is already deleted |
OCI-31195 | XML node 'string' (type=string) does not support this operation |
OCI-31196 | XML nodes over string in size cannot be printed |
OCI-31197 | Error in processing file string |
OCI-31198 | Mismatch in number of bytes transferred due to non-binary mode |
OCI-31199 | Warning in processing file string |
QSM-00501 | unable to initialize Summary Advisor environment |
QSM-00502 | OCI error |
QSM-00503 | out of memory |
QSM-00504 | internal error |
QSM-00505 | syntax error |
QSM-00506 | no fact-tables could be found |
QSM-00507 | no dimensions could be found |
QSM-00508 | statistics missing on tables/columns |
QSM-00509 | invalid parameter |
QSM-00510 | statistics missing on materialized views |
QSM-00511 | invalid fact-tables specified in fact-filter |
QSM-00512 | invalid summaries specified in the retention-list |
QSM-00513 | one or more of the workload tables is missing |
QSM-00514 | the size of must-retain summaries exceeds specified space limit |
QSM-00515 | operation cancelled by user |
QSM-00516 | illegal status detected for run |
QSM-00517 | Summary Advisor requires a COMPATIBLE setting of 8.1.0.0 or greater |
QSM-00518 | Java is not enabled. Please execute INITJVM.SQL and INITQSMA.SQL |
QSM-00519 | Summary Advisor is not installed. Please execute INITQSMA.SQL. |
QSM-00710 | data access error in module string |
QSM-00750 | the specified value string for parameter string is invalid or contains an invalid item |
QSM-00751 | the file string could not be opened for write access |
QSM-00752 | the parameter string contains an invalid combination of options string |
QSM-00753 | the specified value string is out of the acceptable range of string to string for parameter string |
QSM-00754 | task string does not reference a valid workload and therefore cannot be executed |
QSM-00755 | a set of workload statements already exists for workload string |
QSM-00756 | the specified workload string is being used by one or more advisor tasks |
QSM-00757 | the specified workload string is not referenced by task string |
QSM-00758 | the specified parameter string is not valid for workload string |
QSM-00759 | the user string does not exist for the specified workload statement |
QSM-00760 | the import mode string is invalid for the current operation |
QSM-00761 | the priority string is invalid for the current operation |
QSM-00762 | the specified Summary Advisor workload string does not exist |
QSM-00763 | the owner string was not found while validating user-defined workload string.string |
QSM-00764 | the column string was not found in the user-defined workload table string.string |
QSM-00765 | cannot validate user-defined workload because table string.string is invalid. |
QSM-00766 | a SQL statement is required for the current workload operation |
QSM-00767 | a SQL cache is not available to user string |
QSM-00768 | the search condition is invalid for the requested operation |
QSM-00769 | the SQL statement string was not found for workload string |
QSM-00770 | the specified workload string is already referenced by task string |
QSM-00771 | the specified SQL statement cannot be stored in the workload because it has no valid table references |
QSM-00772 | the specified SQL statement cannot be stored in the workload due to a statement error |
QSM-00773 | the parameter string contains the invalid string name string |
QSM-00774 | there are no SQL statements to process for task string |
QSM-00775 | the specified SQL statement cannot be stored in the workload due to invalid table references |
QSM-00776 | the user-defined workload string is missing the following column: string |
QSM-00777 | the specified directive string is unsupported at this time |
QSM-00778 | the specified output filename string is invalid or cannot be accessed |
QSM-00779 | the specified directive conflicts with the existing directive string |
QSM-00780 | the task string could not be executed because the workload string is being modified |
QSM-00781 | the specified value string is invalid for parameter string. Valid keywords are string |
QSM-00782 | the specified value string is an invalid date format for parameter string |
QSM-00783 | the specified value string contains an invalid date for parameter string |
QSM-00784 | the string string referenced in the list string is invalid for parameter string |
QSM-00785 | the directive string is not supported for task string at this time |
QSM-00786 | the name string is invalid for directive string |
QSM-00787 | the tablespace string is invalid for directive string |
QSM-00788 | The requested recommendation does not support direct implementation |
QSM-00789 | The requested recommendation requires user editing and cannot be implemented |
QSM-00790 | the workload string cannot be modified or changed because it is being used by task string |
QSM-00791 | the specified SQL statement cannot be stored in the workload because is contains unsupported statement type |
QSM-00792 | the specified SQL statement cannot be stored in the workload because one or more tables have missing statistics |
QSM-00793 | the specified SQL Tuning Set string does not exist |
QSM-00794 | the statement can not be stored due to a violation of the string filter |
QSM-00795 | the SQL Tuning Set repository has not been implemented |
QSM-00796 | the specified SQL statement cannot be stored in the workload because table string does not have valid statistics |
QSM-00797 | the specified workload string does not exist for the current user |
QSM-00798 | the specified workload string already exists |
QSM-00799 | the user-defined workload table string cannot be found |
QSM-00800 | the specified workload name string is invalid |
QSM-00801 | the specified username string is invalid |
QSM-00802 | An error occurred while implementing action string (string) string. |
QSM-00803 | The STORAGE_CHANGE parameter value string cannot be zero or negative for partial workloads. |
QSM-00804 | not enough space for mandatory access structures |
QSM-00805 | the specified recommendation string value string is invalid |
QSM-00806 | the string parameter value must be specified when STORAGE_MODE is set to TOTAL |
QSM-00807 | the ANALYSIS_SCOPE parameter value contains an incomplete or invalid combination of options. |
QSM-00808 | parameter string only permits a single keyword. Choose one of the following: string |
QSM-00809 | the selected number of recommendations exceeds the maximum value of string |
QSM-00999 | Advisor feature is not currently implemented |
QSM-01001 | query rewrite not enabled |
QSM-01002 | no query rewrite when OPTIMIZER_MODE is rule based |
QSM-01003 | no query rewrite on DDL queries |
QSM-01004 | no query rewrite before view merging |
QSM-01005 | no query rewrite when query has slave SQL |
QSM-01006 | query rewrite disabled for this query block |
QSM-01007 | query has NOREWRITE hint |
QSM-01008 | no query rewrite for update queries |
QSM-01009 | query rewritten with materialized view, string, using text match algorithm |
QSM-01010 | table(s) in the query not found in materialized view, string |
QSM-01011 | when heuristic rewrite not set, rewrite hint required |
QSM-01012 | SAMPLE clause present in FROM |
QSM-01013 | nested aggregates or CONNECT BY/START WITH clause present |
QSM-01014 | top level operator in WHERE clause of the query is an OR |
QSM-01015 | GROUP BY clause has non-columns |
QSM-01016 | Query rewrite does not support, aggregate, string |
QSM-01017 | aggregate argument cannot be converted to canonical form |
QSM-01018 | single table materialized join view rewrite not required |
QSM-01019 | no suitable materialized view found to rewrite this query |
QSM-01020 | materialized view, string, is ineligible |
QSM-01021 | materialized view, string, not found in the hint list |
QSM-01022 | a more optimal materialized view than string was used to rewrite |
QSM-01023 | materialized view, string, has GRANT errors |
QSM-01024 | materialized view, string, has unknown compile errors |
QSM-01025 | materialized view, string, not found |
QSM-01026 | query rewrite is disabled for, string |
QSM-01027 | materialized view, string, is unusable |
QSM-01028 | materialized view, string, is currently being refreshed |
QSM-01029 | materialized view, string, is stale in ENFORCED integrity mode |
QSM-01030 | materialized view, string, has PL/SQL functions in ENFORCED integrity mode |
QSM-01031 | materialized view, string, is stale in TRUSTED integrity mode |
QSM-01032 | materialized view, string, not found |
QSM-01033 | query rewritten with materialized view, string |
QSM-01034 | materialized view, string, needs a dimension level to join table, string |
QSM-01035 | a row level security policy exists on this table |
QSM-01036 | unmatched column, string, present in query after view merging |
QSM-01037 | Query Rewrite failed to allocate the necessary query join graph |
QSM-01038 | logical operator(s) could not be processed |
QSM-01039 | selection present on right hand side of an outer join |
QSM-01040 | match between the materialized view (string) and query join graphs failed |
QSM-01041 | materialized view, string, does not match with a measure in the query |
QSM-01042 | anchor and matching join arc check failed for string |
QSM-01043 | join back attempted on a table to the RHS of a semi or anti join for string |
QSM-01044 | join back attempted on a view for string |
QSM-01046 | complex join back on correlated columns not allowed (string) |
QSM-01047 | complex join back on non-MAV rewrite not allowed (string) |
QSM-01048 | join back level(s) not present (string) |
QSM-01049 | semi-join check failed for materialized view, string |
QSM-01050 | roll-up check failed for materialized view, string |
QSM-01051 | no support for rollup when a window function is present on the column |
QSM-01052 | referential integrity constraint on table, string, not VALID in ENFORCED integrity mode |
QSM-01053 | NORELY referential integrity constraint on table, string, in TRUSTED/STALE TOLERATED integrity mode |
QSM-01054 | no join match between query and summary, string |
QSM-01055 | Query Rewrite failed to allocate the necessary materialized view join graph |
QSM-01056 | no query rewrite for this DDL expression |
QSM-01057 | no query rewrite for this DML expression |
QSM-01058 | MV, string, does not have column, string, for a joinback |
QSM-01059 | HAVING clause in the query block is malformed |
QSM-01060 | illegal subquery in the HAVING clause |
QSM-01061 | illegal query expression |
QSM-01062 | query has one or more manual partition(s) |
QSM-01063 | query has a dictionary table or view |
QSM-01064 | query has a fixed table or view |
QSM-01065 | materialized view, string, cannot compute measure, string, in the query |
QSM-01066 | materialized view, string, does not have the column, string, from query |
QSM-01067 | materialized view, string, cannot support the query measure, string |
QSM-01068 | no dimensions present |
QSM-01069 | summary join graph for, string, does not have table, string |
QSM-01070 | equivalence class manager was not found |
QSM-01071 | query rewrite not possible because a join in materialized view % with table % has eliminated some rows found in query |
QSM-01072 | materialized view, string, and query have different joins between tables, string |
QSM-01073 | query rewrite not possible because materialized view, string, has a join not found in query |
QSM-01074 | query rewrite not possible because materialized view, string, and query have different number of joins between tables, string |
QSM-01075 | materialized view, string, does not support aggregate function, string |
QSM-01076 | no materialized join view was found |
QSM-01077 | materialized view, string, is grouping at a higher level than query |
QSM-01078 | materialized view, string, is marked invalid |
QSM-01079 | DML operation occurred on a table referenced by MV, string |
QSM-01080 | invalid dimension, string |
QSM-01081 | no primary key or row id found for table, string, in MV, string |
QSM-01082 | Joining materialized view, string, with table, string, not possible |
QSM-01083 | query text not available - possible inline view |
QSM-01084 | materialized view string has an anchor table string not found in query |
QSM-01085 | materialized view, string, has a lossy join between tables, string |
QSM-01086 | dimension(s) not present or not used in ENFORCED integrity mode |
QSM-01087 | query grouping on a column that cannot be derived from materialized view, string |
QSM-01089 | an inline view in the query does not have a materialized view |
QSM-01090 | no query rewrite after view merging |
QSM-01091 | cost based optimizer found query rewrite is more expensive |
QSM-01092 | mjv tries to rewrite a semi-join and primary key or rowid missing |
QSM-01093 | anti-join marker not found in materialized join view |
QSM-01094 | outer-join filter not found in materialized join view |
QSM-01095 | no suitable grouping_id found in MV with grouping sets |
QSM-01096 | Materialized view with grouping sets contains duplicates |
QSM-01097 | Materialized view with grouping sets has too long key |
QSM-01098 | mv string clause more restrictive than query string clause |
QSM-01099 | non-tolerated reference to stale portion of mv for table string |
QSM-01100 | containment check failed for mv, string |
QSM-01101 | rollup(s) took place on mv, string |
QSM-01102 | materialized view, string, requires join back to table, string, on column, string |
QSM-01103 | there is a remote table, string, referenced in the query |
QSM-01104 | query is using flashback |
QSM-01105 | no primary key or row id in MV, string, is found for table, string |
QSM-01106 | materialized view, string, is stale with respect to some partition(s) in the base table(s) |
QSM-01107 | Partition Containment Tracking (PCT) rewrite is not allowed |
QSM-01108 | maximum number of disjuncts exceeded in the query string |
QSM-01109 | while rewriting with MV, string, table, string, migrated to query delta |
QSM-01110 | query rewrite not possible with materialized view string because it contains a join between tables (string) that is not present in the query and that potentially eliminates rows needed by the query |
QSM-01111 | no partition key or partition marker found in MV, string |
QSM-01112 | WHERE clause of mv, string, is more restrictive than query |
QSM-01113 | HAVING clause of mv, string, is more restrictive than query |
QSM-01115 | rollup took place on a column with a window function |
QSM-01116 | window function computability checks failed |
QSM-01120 | recursive rewrite not allowed here |
QSM-01121 | materialized view, string, is TRUSTED in ENFORCED integrity mode |
QSM-01123 | self-join algorithm could not resolve multiple instances |
QSM-01124 | set operator materialized view, string, doesn't have a marker column |
QSM-01125 | a more optimal set operator materialized view than string was used to rewrite |
QSM-01126 | query rewritten with set operator materialized view, string |
QSM-01127 | query rewritten with materialized view(s), string |
QSM-01128 | Multi MV rewrite is disabled |
QSM-01129 | query has NO_MULTIMV_REWRITE hint |
QSM-01130 | Multi MV rewrite not allowed if at least one query block has no MVs |
QSM-01131 | query has ONLY_MULTIMV_REWRITE hint |
QSM-01132 | query has a named array type column |
QSM-01133 | query has an ADT column |
QSM-01134 | query has a hidden or nested table column |
QSM-01135 | query has an LOB column |
QSM-01136 | query has a nested table column |
QSM-01137 | dimension level, string, marked as SKIP WHEN NULL |
QSM-01150 | query did not rewrite |
QSM-01168 | query rewrite not possible when Fine Grain Auditing is present on a base table |
QSM-01169 | query rewrite not possible for a CREATE or ALTER VIEW statement |
QSM-01202 | query rewrite not possible when OPTIMIZER_MODE is set to rule based |
QSM-01203 | query rewrite not possible on DDL queries |
QSM-01204 | query rewrite not possible before view merging |
QSM-01205 | query rewrite not possible when query has slave SQL |
QSM-01207 | query rewrite not possible when query has a NOREWRITE hint |
QSM-01208 | query rewrite not possible for update queries |
QSM-01209 | query rewritten with materialized view, string, using text match algorithm |
QSM-01210 | query rewrite not possible because no common table(s) found between materialized view string and query |
QSM-01211 | query rewrite not possible when stored outline does not have a rewrite hint |
QSM-01212 | query rewrite not possible when SAMPLE clause is present in FROM |
QSM-01213 | query rewrite not possible when nested aggregates or CONNECT BY clause or START WITH clause or recursive WITH clause is present |
QSM-01214 | query rewrite not possible if OR is the top level operator in query WHERE clause |
QSM-01215 | query rewrite not possible when query GROUP BY clause has non-columns |
QSM-01218 | query rewrite is likely more expensive due to a single table match between materialized view and query |
QSM-01219 | no suitable materialized view found to rewrite this query |
QSM-01220 | materialized view, string, is disabled, stale or unusable |
QSM-01222 | materialized view string is less optimal than string |
QSM-01241 | query measure cannot be derived from the materialized view string |
QSM-01244 | join back could not be done on a view for string |
QSM-01246 | join back on correlated columns not allowed (string) |
QSM-01247 | join back cannot be done on a materialized view that does not have an aggregate (string) |
QSM-01248 | materialized view does not have the join back level(s) (string) |
QSM-01251 | query rewrite cannot perform rollup due to the presence of a window function |
QSM-01256 | query rewrite not possible for this DDL statement |
QSM-01257 | query rewrite not possible for this DML statement |
QSM-01263 | query rewrite not possible when query references a dictionary table or view |
QSM-01271 | query rewrite not possible because a join in materialized view string with table string has eliminated some rows found in query |
QSM-01273 | query rewrite not possible because materialized view string has a join not found in query |
QSM-01274 | query rewrite not possible because materialized view string and query have different number of joins between tables string |
QSM-01279 | query rewrite not possible because DML operation occurred on a table referenced by materialized view string |
QSM-01281 | query rewrite not possible because either a primary key or a row id is required to join table string with MV string |
QSM-01284 | materialized view string has an anchor table string not found in query |
QSM-01293 | anti-join marker not found in materialized view with joins |
QSM-01295 | no suitable grouping_id found in materialized view with grouping sets |
QSM-01296 | query rewrite not possible because materialized view contains duplicate grouping sets |
QSM-01297 | query rewrite not possible because materialized view with grouping sets has more than 176 different keys |
QSM-01298 | materialized view string clause more restrictive than query string clause |
QSM-01299 | query rewrite not possible because materialized view string is partially stale |
QSM-01303 | query rewrite not possible because query references a remote table string |
QSM-01304 | query rewrite not possible because query is using flashback |
QSM-01307 | Partition Containment Tracking (PCT) rewrite is not allowed |
QSM-01308 | number of 'OR's in query exceeded the maximum value string |
QSM-01316 | window function could not be computed from materialized view string |
QSM-01321 | query rewrite not possible because materialized view string has TRUSTED constraints in ENFORCED integrity mode |
QSM-01332 | query rewrite not possible because query has a named array type column |
QSM-01333 | query rewrite not possible because query has an ADT column |
QSM-01334 | query rewrite not possible because query has a hidden or nested table column |
QSM-01335 | query rewrite not possible because query has an LOB column |
QSM-01336 | the materialized view you specified (string) was not used to rewrite the query |
QSM-01339 | rewrite not supported on inline view aggregate |
QSM-01340 | no inline view match found between query and materialized view(s) |
QSM-01341 | joins between materialized view string and query inline views are different |
QSM-01342 | query rewrite not possible because query has full outer join |
QSM-01343 | general inline view rewrite not possible on remote objects |
QSM-01344 | general inline view rewrite not possible on this WHERE clause construct |
QSM-01345 | general inline view rewrite not possible when inline view has subquery |
QSM-01346 | general inline view rewrite not possible with nested inline views |
QSM-01347 | a query inline view could not be matched with any materialized view inline view |
QSM-01348 | an invalid predicate was found in an inline view |
QSM-01349 | general inline view cannot be supported on this inline view |
QSM-01350 | query rewrite cannot support this inline view |
QSM-01351 | query inline view has no matching objects with any materialized view inline views |
QSM-01352 | SELECT lists of the query and materialized view inline views do not match |
QSM-01353 | no query rewrite on remote objects unless integrity mode is set to stale_tolerated |
QSM-01354 | query rewrite is disabled for remote objects |
QSM-01355 | multi-mv rewrite not possible in the presence of remote objects |
QSM-01356 | query rewrite against cube-organized materialized views not possible when OLAP option is off |
QSM-01509 | equivalence, string, matched query text |
QSM-01522 | a more optimal equivlanece than string was used to rewrite |
QSM-01526 | query rewrite is disabled for equivalence, string |
QSM-01533 | query rewritten with equivalence, string |
QSM-01565 | equivalence, string, cannot compute measure, string, in the query |
QSM-01567 | equivalence, string, cannot support the query measure, string |
QSM-01572 | equivalence, string, and query have different joins between tables, string |
QSM-01582 | Joining equivalence, string, with table, string, not possible |
QSM-01584 | equivalence, string, has anchor, string, not found in query |
QSM-01601 | rollup(s) took place on equivalence, string |
QSM-01602 | equivalence, string, requires join back to table, string, on column, string |
QSM-01610 | a lossy join in equivalence, string, between tables, string, not found in query |
QSM-01617 | equivalence definition is disabled |
QSM-01618 | equivalence, string, is enabled for text match rewrite only |
QSM-01619 | equivalence cannot be used in ENFORCED integrity mode |
QSM-01621 | join backs to base tables not allowed with an equivalence |
QSM-01709 | query rewritten with equivalence, string, using text match algorithm |
QSM-01784 | equivalence string has an anchor table string not found in query |
QSM-01837 | recursive query rewrite on equivalence, string, not permitted |
QSM-01838 | semijoin transformation not supported on equivalence |
QSM-02001 | clustered mv container table |
QSM-02002 | DISTINCT aggregate measure in SELECT list |
QSM-02003 | aggregate function nested within an expression |
QSM-02004 | grouping column omitted from SELECT list |
QSM-02005 | named view in FROM list |
QSM-02006 | subquery in FROM list |
QSM-02007 | multiple instances of the same table or view |
QSM-02008 | non-join filter condition in WHERE or HAVING clause |
QSM-02009 | non-inner join |
QSM-02010 | join predicate with operator other than equals (=) |
QSM-02011 | a HAVING clause is present |
QSM-02012 | a CONNECT BY clause is present |
QSM-02013 | SELECT list includes a RAW data type expression |
QSM-02014 | GROUP BY expression other than a column |
QSM-02015 | Index Organized Table (IOT) present in FROM list |
QSM-02016 | clustered table in FROM list |
QSM-02017 | subquery present in the HAVING clause |
QSM-02018 | subquery present in the WHERE clause |
QSM-02019 | mv references another mv in FROM clause |
QSM-02020 | container column not in SELECT list with NOT NULL constraint |
QSM-02021 | set operator encountered in mv |
QSM-02022 | aggregate selections |
QSM-02023 | nested cursor |
QSM-02024 | no GROUP BY clause |
QSM-02025 | no aggregate functions |
QSM-02026 | non-AND conjunction in WHERE clause |
QSM-02027 | group by ROLLUP |
QSM-02028 | group by CUBE |
QSM-02029 | PL/SQL function invocation |
QSM-02030 | reduced precision specified for prebuilt mv |
QSM-02031 | materialized view cannot support any type of query rewrite |
QSM-02032 | no joins are present in the WHERE clause |
QSM-02033 | no filter conditions are present in the WHERE clause |
QSM-02034 | no joins are present in the HAVING clause |
QSM-02035 | no filter conditions are present in the HAVING clause |
QSM-02036 | in-list present in mv |
QSM-02037 | cannot evaluate constant expression at compile time |
QSM-02038 | Partition Change Tracking (PCT) is enabled |
QSM-02039 | top level mv query uses grouping sets |
QSM-02040 | top level query contains GSets and the key is too long for rewrite |
QSM-02041 | nested aggregate function |
QSM-02042 | view or subquery in from list |
QSM-02044 | ORDER BY clause in mv |
QSM-02045 | START WITH clause in mv |
QSM-02047 | window function in mv |
QSM-02048 | outer join in mv |
QSM-02049 | subquery using the ANY clause in mv |
QSM-02050 | subquery using the ALL clause in mv |
QSM-02051 | subquery using the NOT EXISTS clause in mv |
QSM-02052 | subquery using a select list in mv |
QSM-02053 | collection subquery in mv |
QSM-02054 | DISTINCT clause in select list in mv |
QSM-02055 | mv references a packed object table or view |
QSM-02056 | correlated variable and outer join in mv |
QSM-02057 | ROWNUM referenced in mv |
QSM-02058 | set operator in mv and compatibility mode is less than 9.0 |
QSM-02059 | join may produce duplicate rows in mv |
QSM-02061 | one or more joins present in mv |
QSM-02062 | GROUP BY clause in mv |
QSM-02063 | aggregate function in mv |
QSM-02064 | subquery in mv |
QSM-02066 | Oracle error: see RELATED_NUM and RELATED_TEXT for details |
QSM-02067 | no partition key or PMARKER or join dependent expression in select list |
QSM-02068 | relation is not a partitioned table |
QSM-02069 | PCT not supported with multi-column partition key |
QSM-02070 | PCT not supported with this type of partitioning |
QSM-02071 | internal error: undefined PCT failure code |
QSM-02072 | requirements not satisfied for fast refresh of nested mv |
QSM-02073 | non-primary key RepAPI mv is not fast refreshable |
QSM-02074 | materialized view over Heterogeneous Services link |
QSM-02075 | materialized view on synonym |
QSM-02076 | sequence number in the mv log is newer than last refresh |
QSM-02077 | mv log is newer than last full refresh |
QSM-02078 | mv log must have new values |
QSM-02079 | mv log must have ROWID |
QSM-02080 | mv log must have primary key |
QSM-02081 | mv log does not have all necessary columns |
QSM-02082 | problem with mv log |
QSM-02083 | mv references PL/SQL function that maintains state |
QSM-02084 | DISTINCT clause on a duplicate sensitive aggregate function |
QSM-02086 | mv uses the MIN or MAX aggregate functions |
QSM-02088 | mv omits at least one grouping key from the select list |
QSM-02090 | SELECT includes an expression that is not just a column |
QSM-02091 | mv references a non-repeatable or session-sensitive expression |
QSM-02092 | mv references a sequence number |
QSM-02093 | mv uses an object REF clause |
QSM-02096 | mv references a named view |
QSM-02099 | mv references a remote table or view in the FROM list |
QSM-02101 | mv references a synonym in the FROM list |
QSM-02102 | mv FROM list references an object in the SYS schema |
QSM-02104 | aggregate function in a filter condition in the HAVING clause |
QSM-02106 | mv uses a filter condition in the WHERE or HAVING clause |
QSM-02112 | top level query has LEFT OUTER, RIGHT OUTER or FULL OUTER join |
QSM-02113 | expression in select list references multiple tables or views |
QSM-02114 | no GROUP BY clause, no aggregates and not >= 9.0 compatibility |
QSM-02115 | mv references a remote object and is refreshed ON COMMIT |
QSM-02116 | mupltiple master sites |
QSM-02117 | missing GROUPING_ID or GROUPING functions on GROUP BY column(s) |
QSM-02118 | duplicate grouping sets |
QSM-02119 | internal error while analyzing required supporting aggregates |
QSM-02120 | compatibility mode must be 9.0 or higher |
QSM-02121 | set operator in a context not supported for fast refresh |
QSM-02122 | compatibility mode must be 8.1 or higher |
QSM-02123 | subquery and UNION mv's must be primary key mv's |
QSM-02124 | object type in WHERE clause |
QSM-02125 | subquery join conditions don't meet requirements for capability |
QSM-02126 | no rowid at master site |
QSM-02127 | not supported for this type mv by Oracle version at master site |
QSM-02128 | does not meet the requirements of a primary key mv |
QSM-02129 | join or filter condition(s) are complex |
QSM-02130 | expression not supported for fast refresh |
QSM-02131 | agg(expr) requires correspondng SUM(expr) function |
QSM-02132 | agg(expr) requires correspondng COUNT(expr) function |
QSM-02133 | agg(expr) requires correspondng MIN(expr) function |
QSM-02134 | agg(expr) requires correspondng MAX(expr) function |
QSM-02135 | agg(expr) requires correspondng AVG(expr) function |
QSM-02136 | agg(expr) requires correspondng VARIANCE(expr) function |
QSM-02137 | agg(expr) requires correspondng STDDEV(expr) function |
QSM-02138 | agg(expr) requires correspondng agg(expr*expr) function |
QSM-02139 | agg(expr) requires correspondng agg(expr+expr) function |
QSM-02140 | agg(expr) requires correspondng SUM(expr*expr) function |
QSM-02141 | the reason why the capability is disabled has escaped analysis |
QSM-02142 | COUNT(*) is not present in the select list |
QSM-02143 | SUM(expr) without COUNT(expr) |
QSM-02144 | aggregate functions are present without a GROUP BY clause |
QSM-02145 | GROUP BY clause is present but no aggregate functions are used |
QSM-02146 | see the reason why REFRESH_FAST_AFTER_INSERT is disabled |
QSM-02147 | default date format is sensitive to session settings |
QSM-02148 | many to many subquery joins require 9.0 compatibility or higher |
QSM-02149 | ON COMMIT with this MV requires 9.0 compatibility or higher |
QSM-02150 | select lists must be identical across the UNION operator |
QSM-02151 | subquery or named view in FROM list and < 9.0 compatibility |
QSM-02152 | subquery or named view in FROM list even after view merging |
QSM-02153 | inline view or subquery in FROM list not supported for this type MV |
QSM-02154 | MV is not fast refreshable even with view merging |
QSM-02161 | see the reason why REFRESH_FAST_AFTER_ONETAB_DML is disabled |
QSM-02162 | the detail table does not have a materialized view log |
QSM-02163 | cannot use object id columns from materialized view log |
QSM-02169 | the materialized view contains partition extended table name |
QSM-02170 | tables must be identical across the UNION operator |
QSM-02171 | the materialized view has a join operation in the outer UNION block |
QSM-02173 | the unique constraints does not exist on the join columns of the inner table |
QSM-02174 | the materialized view does not have a UNION ALL marker column |
QSM-02175 | some query block in UNION ALL MV is not fast refreshable |
QSM-02176 | MV with UNION ALL in a view is too complex |
QSM-02177 | MV with UNION ALL in a view must match the view's SELECT list |
QSM-02178 | MV has a view with UNION ALL that is not fast refreshable |
QSM-02179 | MV with UNION ALL requires compatibility >= 9.2 |
QSM-02180 | no primary key constraint in the master table |
QSM-02181 | a SPREADSHEET clause is present |
QSM-02182 | PCT is enabled through a join dependency |
QSM-02183 | Expression to enable PCT not in PARTITION BY of analytic function or SPREADSHEET |
QSM-02184 | Expression to enable PCT cannot be rolled up |
QSM-02185 | no partition key or PMARKER in select list |
QSM-02186 | PARTITIONED OUTER JOIN is present |
QSM-02187 | materialized view on external table |
QSM-02188 | named view in FROM list not supported for this type MV |
QSM-02189 | materialized view definition changes |
QSM-02190 | SQL PIVOT or UNPIVOT is present |
QSM-02191 | types of MV logs are not compatible |
QSM-02192 | commit SCN based MV log is not in consistent state |
QSM-02193 | unsupported MV on commit SCN based MV logs |
QSM-02194 | CASE expressions present in materialized view |
QSM-02195 | PCT FAST REFRESH is not possible if query contains a named view |
QSM-02196 | PCT FAST REFRESH is not possible if query contains an inline view |
QSM-02197 | PCT FAST REFRESH is not possible if query contains a remote table |
QSM-02198 | PCT FAST REFRESH is not possible if HAVING clause includes a subquery |
QSM-02199 | PCT FAST REFRESH is not possible if WHERE clause includes a subquery |
QSM-02200 | PCT FAST REFRESH is not possible if query contains LEFT OUTER, RIGHT OUTER or FULL OUTER JOIN |
QSM-02201 | PCT FAST REFRESH is not possible if there is a self join or self cartesian product in query |
QSM-02202 | PCT FAST REFRESH is not possible if query has ORDER BY clause |
QSM-02203 | PCT FAST REFRESH is not possible if query has set operand query blocks |
QSM-02204 | PCT FAST REFRESH is not possible if query has an inner query |
QSM-02205 | PCT FAST REFRESH is not possible if there is a subquery inside select-list |
QSM-02206 | PCT FAST REFRESH is not possible because this query join may produce extra duplicate rows |
QSM-02207 | PCT FAST REFRESH is not possible for complex queries |
QSM-02208 | subquery using the NOT IN clause in materialized view |
QSM-03112 | Invalid CREATE MATERIALIZED VIEW statement string |
QSM-03113 | Cannot tune the MATERIALIZED VIEW statement string |
QSM-03114 | Cannot tune FOR UPDATE materialized view |
QSM-03115 | Cannot tune materialized view ON PREBUILT table |
QSM-03116 | The materialized view is already optimal and cannot be tuned any further |
QSM-03117 | Cannot tune the materialized view to be fast refreshable |
QSM-03118 | Cannot tune the materialized view for general rewrite |
QSM-03119 | The WHERE/HAVING clause is too complex for general query rewrite |
QSM-03120 | Cannot create materialized view log on encrypted columns |
RMAN-00201 | Do you really want to execute the above repair (enter YES or NO)? |
RMAN-00202 | Do you want to open the database (enter YES or NO)? |
RMAN-00203 | Do you want to open resetlogs the database (enter YES or NO)? |
RMAN-00204 | Do you really want to delete the above objects (enter YES or NO)? |
RMAN-00205 | Do you really want to drop all backups and the database (enter YES or NO)? |
RMAN-00206 | Do you really want to drop the database (enter YES or NO)? |
RMAN-00207 | Do you really want to unregister the database (enter YES or NO)? |
RMAN-00208 | Want to unregister the database with target db_unique_name (enter YES or NO)? |
RMAN-00209 | Do you really want to change the above failures (enter YES or NO)? |
RMAN-00210 | Do you really want to catalog the above files (enter YES or NO)? |
RMAN-00211 | Error occurred getting response - assuming NO response |
RMAN-00212 | "string" is an invalid response - please re-enter. |
RMAN-00550 | parser package failed to load |
RMAN-00551 | initialization of parser package failed |
RMAN-00552 | syntax error in command line arguments |
RMAN-00553 | internal recovery manager package failed to load |
RMAN-00554 | initialization of internal recovery manager package failed |
RMAN-00555 | target database connect string must be specified |
RMAN-00556 | could not open CMDFILE "string" |
RMAN-00557 | could not open MSGLOG "string" |
RMAN-00558 | error encountered while parsing input commands |
RMAN-00562 | username too long |
RMAN-00563 | password too long |
RMAN-00564 | host data too long |
RMAN-00565 | unable to read input file |
RMAN-00566 | could not open TRACE "string" |
RMAN-00567 | Recovery Manager could not print some error messages |
RMAN-00568 | user interrupt received |
RMAN-00569 | =============== ERROR MESSAGE STACK FOLLOWS =============== |
RMAN-00570 | **end-of-file** |
RMAN-00571 | =========================================================== |
RMAN-00572 | waiting for DBMS_PIPE input |
RMAN-00573 | DBMS_PIPE.NEXT_ITEM_TIME returned unknown type code: number |
RMAN-00574 | rman aborting due to errors reading/writing DBMS_PIPE |
RMAN-00575 | timeout while trying to write to DBMS_PIPE |
RMAN-00576 | PIPE cannot be used with CMDFILE |
RMAN-00577 | PIPE requires that TARGET be specified on the command line |
RMAN-00578 | pipe string is not private and owned by SYS |
RMAN-00579 | SCRIPT cannot be used with CMDFILE |
RMAN-00600 | internal error, arguments [string] [string] [string] [string] [string] |
RMAN-00601 | fatal error in recovery manager |
RMAN-00700 | SCRIPT requires that TARGET be specified on the command line |
RMAN-00701 | SCRIPT requires that CATALOG be specified on the command line |
RMAN-00702 | The command has no syntax errors |
RMAN-00703 | The cmdfile has no syntax errors |
RMAN-01006 | error signaled during parse |
RMAN-01007 | at line number column number file: string |
RMAN-01008 | the bad identifier was: string |
RMAN-01009 | syntax error: found "string": expecting one of: "string" |
RMAN-02000 | wrong message file version (msg number not found) |
RMAN-02001 | unrecognized punctuation symbol "string" |
RMAN-02002 | unexpected end of input file reached |
RMAN-02003 | unrecognized character: string |
RMAN-02004 | quoted string too big |
RMAN-02005 | token too big |
RMAN-02006 | script line too long |
RMAN-02007 | Integer value overflow |
RMAN-02008 | no value exists for variable "string" |
RMAN-02009 | unexpected end of command file reached |
RMAN-03000 | recovery manager compiler component initialization failed |
RMAN-03001 | recovery manager command sequencer component initialization failed |
RMAN-03002 | failure of string command at string |
RMAN-03003 | command not implemented yet: string |
RMAN-03004 | fatal error during execution of command |
RMAN-03008 | error while performing automatic resync of recovery catalog |
RMAN-03009 | failure of string command on string channel at string |
RMAN-03010 | fatal error during library cache pre-loading |
RMAN-03011 | Recovery Managerstring |
RMAN-03012 | fatal error during compilation of command |
RMAN-03013 | Copyright (c) 1995, 2003, Oracle Corporation. All rights reserved. |
RMAN-03014 | implicit resync of recovery catalog failed |
RMAN-03015 | error occurred in stored script string |
RMAN-03017 | recursion detected in stored script string |
RMAN-03018 | asynchronous RPCs are working correctly |
RMAN-03019 | asynchronous RPCs are NOT working |
RMAN-03020 | asynchronous RPC test will take 1 minute |
RMAN-03023 | executing command: string |
RMAN-03028 | fatal error code for command string : number |
RMAN-03029 | echo set on |
RMAN-03030 | echo set off |
RMAN-03031 | this option of set command needs to be used inside a run block |
RMAN-03032 | this option of set command needs to be used outside of a run block |
RMAN-03033 | current log archived |
RMAN-03034 | LEVEL number is invalid. LEVEL must be between string and string |
RMAN-03035 | Debugging turned off |
RMAN-03036 | Debugging set to level=number, types=string |
RMAN-03037 | Spooling started in log file: string |
RMAN-03038 | Spooling started in trace file: string |
RMAN-03039 | Spooling for log turned off |
RMAN-03040 | Spooling for trace turned off |
RMAN-03042 | error while analyzing automatic repair options |
RMAN-03090 | Starting string at string |
RMAN-03091 | Finished string at string |
RMAN-03098 | stringRMAN-number: stringstring |
RMAN-03099 | job cancelled at user request |
RMAN-03999 | Oracle error occurred while while converting a date: ORA-number: string |
RMAN-04000 | memory allocation failure |
RMAN-04001 | heap initialization failure |
RMAN-04002 | OCIPI failed, ORA-string |
RMAN-04003 | OCIINIT failed |
RMAN-04004 | error from recovery catalog database: string |
RMAN-04005 | error from target database: string |
RMAN-04006 | error from auxiliary database: string |
RMAN-04007 | WARNING from recovery catalog database: string |
RMAN-04008 | WARNING from target database: string |
RMAN-04009 | WARNING from auxiliary database: string |
RMAN-04010 | target database Password: |
RMAN-04011 | recovery catalog database Password: |
RMAN-04012 | auxiliary database Password: |
RMAN-04013 | must connect before startup |
RMAN-04014 | startup failed: string |
RMAN-04015 | error setting target database character set to string |
RMAN-04016 | could not get OCI error handle |
RMAN-04017 | startup error description: string |
RMAN-04020 | target database name "string" does not match channel's name: "string" |
RMAN-04021 | target database DBID string does not match channel's DBID string |
RMAN-04022 | target database mount id string does not match channel's mount id string |
RMAN-04024 | starting Oracle instance without parameter file for retrieval of spfile |
RMAN-04025 | unable to generate a temporary file |
RMAN-04026 | unable to open a temporary file: "string" |
RMAN-04027 | unable to write to a temporary file: "string" |
RMAN-04031 | initialization parameters used for automatic instance: string |
RMAN-04032 | using contents of file string |
RMAN-04033 | cannot open auxiliary parameter file string |
RMAN-04034 | source recovery catalog database Password: |
RMAN-04035 | error from source recovery catalog database: string |
RMAN-04036 | WARNING from source recovery catalog database: string |
RMAN-05000 | CONFIGURE AUXNAME required for datafile string |
RMAN-05001 | auxiliary file name string conflicts with a file used by the target database |
RMAN-05002 | aborting Tablespace Point-in-Time Recovery |
RMAN-05003 | Tablespace Point-in-Time Recovery is not allowed for tablespace string |
RMAN-05004 | target database log mode is NOARCHIVELOG |
RMAN-05005 | Tablespace Point-in-Time Recovery is not allowed for re-created tablespace string |
RMAN-05006 | cannot recover clone standby single tablespaces |
RMAN-05007 | no channel allocated |
RMAN-05009 | Block Media Recovery requires Enterprise Edition |
RMAN-05010 | target database must be opened in READ WRITE mode for Tablespace Point-in-Time Recovery |
RMAN-05011 | auxiliary instance must be in NOMOUNT state for Tablespace Point-in-Time Recovery |
RMAN-05013 | auxiliary control file name string conflicts with a file used by the target database |
RMAN-05014 | Tablespaces with undo segments were not found in recovery catalog |
RMAN-05015 | WARNING: not enough information in recovery catalog for specified point-in-time recovery |
RMAN-05016 | failover to previous backup |
RMAN-05017 | no copy of datafile number found to recover |
RMAN-05018 | some datafile copies cannot be recovered, aborting the RECOVER command |
RMAN-05019 | WARNING: no channel of required type allocated to recover copy of datafile number |
RMAN-05020 | cannot specify AUXILIARY DESTINATION option for normal recovery |
RMAN-05021 | this configuration cannot be changed for a BACKUP or STANDBY control file |
RMAN-05022 | TRANSPORT TABLESPACE may not be used with user-managed auxiliary instance |
RMAN-05023 | TABLESPACE DESTINATION required |
RMAN-05024 | List of tablespaces presumed to have UNDO segments |
RMAN-05025 | Tablespace string |
RMAN-05026 | WARNING: presuming following set of tablespaces applies to specified point-in-time |
RMAN-05027 | List of tablespaces expected to have UNDO segments |
RMAN-05028 | Tablespace string |
RMAN-05029 | UNDO TABLESPACE clause is only valid for Tablespace Point-in-Time Recovery |
RMAN-05030 | CLONE clause cannot be used with Tablespace Point-in-Time Recovery |
RMAN-05031 | cannot specify UNDO TABLESPACE clause for normal recovery |
RMAN-05032 | datafile string will be created automatically during restore operation |
RMAN-05033 | Media recovery start SCN is string |
RMAN-05034 | Recovery must be done beyond SCN string to clear datafile fuzziness |
RMAN-05035 | archived logs generated after SCN string not found in repository |
RMAN-05036 | FOR DB_UNIQUE_NAME option cannot be used for this configuration |
RMAN-05037 | FOR DB_UNIQUE_NAME option cannot be used in nocatalog mode |
RMAN-05038 | unable to determine UNTIL SCN for TRANSPORT |
RMAN-05039 | One or more auxiliary set datafiles could not be removed |
RMAN-05040 | List of tablespaces that have been dropped from the target database: |
RMAN-05041 | Error during export of metadata |
RMAN-05042 | Error during import of metadata |
RMAN-05043 | Tablespace string |
RMAN-05044 | Performing export of metadata... |