RMAN-04006: error from auxiliary database: string

RMAN-04006: error from auxiliary database: string

Cause: Oracle error signaled by auxiliary database. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-04005: error from target database: string

RMAN-04005: error from target database: string

Cause: Oracle error signaled by target database. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-04004: error from recovery catalog database: string

RMAN-04004: error from recovery catalog database: string

Cause: Oracle error signaled by catalog database. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-04003: ociinit failed

RMAN-04003: ociinit failed

Cause: The call to OCIEnvInit failed.

Action: This error should not normally happen. Contact Oracle Customer Support.

RMAN-04002: ocipi failed, ORA-string

RMAN-04002: ocipi failed, ORA-string

Cause: OCI process level initialization failed.

Action: This error should not normally occur.

RMAN-04001: heap initialization failure

RMAN-04001: heap initialization failure

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-04000: memory allocation failure

RMAN-04000: memory allocation failure

Cause: A memory allocation request could not be satisified.

Action: Increase the amount of memory available to RMAN.

RMAN-03999: Oracle error occurred while while converting a date: ORA-number: string

RMAN-03999: Oracle error occurred while while converting a date: ORA-number: string

Cause: Internal error converting a date.

Action: Contact Oracle Customer Support.

RMAN-03099: job cancelled at user request

RMAN-03099: job cancelled at user request

Cause: The user interrupted the current job.

Action: None.

RMAN-03098: %-*sRMAN-number: stringstring

RMAN-03098: %-*sRMAN-number: stringstring

Cause: This is the message prefix with a possible indentation.

Action: No action is required.

RMAN-03091: Finished string at string

RMAN-03091: Finished string at string

Cause: This is an informational message only.

Action: No action is required.

RMAN-03090: Starting string at string

RMAN-03090: Starting string at string

Cause: This is an informational message only.

Action: No action is required.

RMAN-03040: Spooling for trace turned off

RMAN-03040: Spooling for trace turned off

Cause: a SPOOL TRACE TO ... comand was issued

Action: No action is required.

RMAN-03039: Spooling for log turned off

RMAN-03039: Spooling for log turned off

Cause: a SPOOL LOG OFF comand was issued

Action: No action is required.

RMAN-03038: Spooling started in trace file: string

RMAN-03038: Spooling started in trace file: string

Cause: a SPOOL TRACE TO ... comand was issued

Action: No action is required.

RMAN-03037: Spooling started in log file: string

RMAN-03037: Spooling started in log file: string

Cause: a SPOOL LOG TO ... comand was issued

Action: No action is required.

RMAN-03036: Debugging set to level=number, types=string

RMAN-03036: Debugging set to level=number, types=string

Cause: a DEBUG comand was issued

Action: No action is required.

RMAN-03035: Debugging turned off

RMAN-03035: Debugging turned off

Cause: a DEBUG OFF comand was issued

Action: No action is required.

RMAN-03034: LEVEL number is invalid. LEVEL must be between string and string

RMAN-03034: LEVEL number is invalid. LEVEL must be between string and string

Cause: An invalid DEBUG LEVEL was used.

Action: Change the DEBUG LEVEL argument.

RMAN-03033: current log archived

RMAN-03033: current log archived

Cause: A ALTER SYSTEM ARCHIVE LOG CURRENT command completed successfully.

Action: None, this is an informational message.

RMAN-03032: this option of set command needs to be used outside of a run block

RMAN-03032: this option of set command needs to be used outside of a run block

Cause: The option used with the SET command is not valid inside of a run block.

Action: Change the SET command or place it outside a run block.

RMAN-03031: this option of set command needs to be used inside a run block

RMAN-03031: this option of set command needs to be used inside a run block

Cause: The option used with the SET command is not valid outside a run block.

Action: Change the SET command or place it inside a run block.

RMAN-03030: echo set off

RMAN-03030: echo set off

Cause: a SET ECHO OFF command was issued

Action: No action is required.

RMAN-03029: echo set on

RMAN-03029: echo set on

Cause: a SET ECHO ON command was issued

Action: No action is required.

RMAN-03028: fatal error code for command string : number

RMAN-03028: fatal error code for command string : number

Cause: Informational message. This preceeds error 3012.

Action: No action is required.

RMAN-03023: executing command: string

RMAN-03023: executing command: string

Cause: This is an informational message only.

Action: No action is required.

RMAN-03020: asynhronous RPC test will take 1 minute

RMAN-03020: asynhronous RPC test will take 1 minute

Cause: This is an informational message only.

Action: No action is required.

RMAN-03019: asynchronous RPCs are NOT working

RMAN-03019: asynchronous RPCs are NOT working

Cause: The RPCTEST command has determined that RPCs are not executing asynchronously. Instead, they are blocking. This is caused by using a SQL*NET driver that does not support non-blocking UPI.

Action: Try using a different SQL*NET driver.

RMAN-03018: asynchronous RPCs are working correctly

RMAN-03018: asynchronous RPCs are working correctly

Cause: This is an informational message only.

Action: No action is required.

RMAN-03017: recursion detected in stored script string

RMAN-03017: recursion detected in stored script string

Cause: A stored script is calling itself or another script which calls itself.

Action: Remove the recusion.

RMAN-03015: error occurred in stored script string

RMAN-03015: error occurred in stored script string

Cause: This is an informational message only.

Action: No action is required.

RMAN-03014: implicit resync of recovery catalog failed

RMAN-03014: implicit resync of recovery catalog failed

Cause: of the failure.

Action: No action is required.

RMAN-03013: Copyright (c) 1995, 2003, Oracle Corporation. All rights reserved.

RMAN-03013: Copyright (c) 1995, 2003, Oracle Corporation. All rights reserved.

Cause: This is the copyright banner

Action: No action is required.

RMAN-03012: fatal error during compilation of command

RMAN-03012: fatal error during compilation of command

Cause: A fatal error occurred during compilation of a command.

Action: This message should be accompanied by other errors explaining the cause of the failure.

RMAN-03011: Recovery Managerstring

RMAN-03011: Recovery Managerstring

Cause: This is the RMAN banner

Action: No action is required.

RMAN-03010: fatal error during library cache pre-loading

RMAN-03010: fatal error during library cache pre-loading

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-03009: failure of string command on string channel at string

RMAN-03009: failure of string command on string channel at string

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-03008: error while performing automatic resync of recovery catalog

RMAN-03008: error while performing automatic resync of recovery catalog

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-03004: fatal error during execution of command

RMAN-03004: fatal error during execution of command

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-03003: command not implemented yet: string

RMAN-03003: command not implemented yet: string

Cause: The command is not implemented in the current release.

Action: Avoid using the command.

RMAN-03002: failure of string command at string

RMAN-03002: failure of string command at string

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-03001: recovery manager command sequencer component initialization failed

RMAN-03001: recovery manager command sequencer component initialization failed

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-03000: recovery manager compiler component initialization failed

RMAN-03000: recovery manager compiler component initialization failed

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-02007: Integer value overflow

RMAN-02007: Integer value overflow

Cause: Parser failed to convert input string to integer

Action: Acceptable values for integer are from 0 to 2147483648. Retry command using valid integer value.

RMAN-02006: script line too long

RMAN-02006: script line too long

Cause: a line longer than 500 bytes was encountered

Action: break the line up into shorter lines

RMAN-02005: token too big

RMAN-02005: token too big

Cause: A token longer than 1000 bytes was encountered

Action: Tokens must be separated by whitespace or punctuation. Either add the missing whitespace or punctuation, or shorten the token.

RMAN-02004: quoted string too big

RMAN-02004: quoted string too big

Cause: A quoted string longer than 2000 bytes was encountered.

Action: This may be caused by a missing close quote. If so, add the missing quote, otherwise shorten the string.

RMAN-02003: unrecognized character: string

RMAN-02003: unrecognized character: string

Cause: An input character that is neither an alpha, digit, or punctuation was encountered.

Action: Remove the character.

RMAN-02002: unexpected end of input file reached

RMAN-02002: unexpected end of input file reached

Cause: This is probably caused by failure to supply the closing quote for a quoted string.

Action: Correct the input.

RMAN-02001: unrecognized punctuation symbol string

RMAN-02001: unrecognized punctuation symbol string

Cause: An illegal punctuation character was encountered.

Action: Remove the illegal character.

RMAN-02000: wrong message file version (msg number not found)

RMAN-02000: wrong message file version (msg number not found)

Cause: The rmanxx.msb file is not the correct version.

Action: Check that the installation was done correctly. The RMAN binary (executable, load module, whatever it is called on your O or S) and the rmanxx.msb file must be from the same version, release, and patch level.

RMAN-06081: error reading datafile header for datafile string, code string

RMAN-06081: error reading datafile header for datafile string, code string

Cause: X$KCVFH returned the specified code in the hxerr column when it was queried for the specified datafile.

Action: Ensure the datafile exists and is readable. Using a newer release of Recovery Manager may return a more meaningful error message. If you have no newer version of Recovery Manager, contact Oracle Customer Support.

RMAN-06080: SWITCH required for datafile string

RMAN-06080: SWITCH required for datafile string

Cause: The control file record for this datafile is for an older incarnation of the datafile. A SWITCH command must be issued to updated the control file before doing RECOVER.

Action: Issue SWITCH command then retry RECOVER.

RMAN-06079: database must be mounted to perform recovery

RMAN-06079: database must be mounted to perform recovery

Cause: A RECOVER command was issued, but the target database is not mounted.

Action: Issue ALTER DATABASE MOUNT.

RMAN-06078: the control file is older than datafile string

RMAN-06078: the control file is older than datafile string

Cause: The control file appears to be older than the specified datafile, but it is not marked as a backup control file. This indicates that the control file has been replaced with an older version. This error does not occur when a backup controlfile which was created via Recovery Manager or the ALTER DATABASE BACKUP CONTROLFILE command is restored because such controlfiles are marked as backups.

Action: RESTORE a control file and perform RECOVER DATABASE.

RMAN-06077: datafile string is a different version than contained in the control file

RMAN-06077: datafile string is a different version than contained in the control file

Cause: The control file entry for this datafile specifies a different version of this datafile. Different versions of a datafile can exist when a tablespace is dropped, and a new tablespace is created which reuses the same datafile numbers.

Action: If the datafile is correct, the fix the control file by using the SWITCH command. Otherwise, RESTORE the correct version of this datafile and retry the RECOVER command.

RMAN-06076: datafile string contains wrong datafile

RMAN-06076: datafile string contains wrong datafile

Cause: The datafile header indicates the file contains a different datafile number.

Action: RESTORE the datafile, and then retry the RECOVER command.

RMAN-06075: datafile string does not belong to this database

RMAN-06075: datafile string does not belong to this database

Cause: The file header indicates that this file belongs to some other ORACLE database.

Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

RMAN-06074: file string is not an ORACLE datafile

RMAN-06074: file string is not an ORACLE datafile

Cause: The file header indicates that this file is not a datafile. The file may have been overlaid or corrupted.

Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

RMAN-06073: file header is corrupt for datafile string

RMAN-06073: file header is corrupt for datafile string

Cause: ORACLE detected a corruption in the file header. A media failure has probably occurred.

Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command.

RMAN-06071: could not open datafile string

RMAN-06071: could not open datafile string

Cause: An error was encountered when trying to open the specified datafile.

Action: Ensure that the datafile exists and is accessible.

RMAN-06070: DBWR could not identify datafile string

RMAN-06070: DBWR could not identify datafile string

Cause: DBWR could not find the specified datafile.

Action: Ensure that the datafile exists and is accessible.

RMAN-06069: the filename for datafile string is missing in the control file

RMAN-06069: the filename for datafile string is missing in the control file

Cause: Media recovery of a backup control file added this datafile to the control file, but it does not set the filename because that is unsafe.

Action: If the datafile is on disk, then issue ALTER DATABASE RENAME to correct the control file. Otherwise, RESTORE the datafile, and then use SWITCH to make it known to the control file. If the tablespace containing this datafile will be dropped, then reissue the RECOVER command with a SKIP clause to skip recovery of this tablespace.

RMAN-06067: RECOVER DATABASE required with a backup or created control file

RMAN-06067: RECOVER DATABASE required with a backup or created control file

Cause: The control file has been restored from a backup or was created via ALTER DATABASE CREATE CONTROLFILE.

Action: Use the RECOVER DATABASE command to perform the recovery.

RMAN-06066: the target database must be mounted when issuing a RECOVER command

RMAN-06066: the target database must be mounted when issuing a RECOVER command

Cause: A RECOVER command was issued, but the target database control file is not mounted.

Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.

RMAN-06065: The backup operand (string( conflicts with another specified operand.

RMAN-06065: The backup operand (string( conflicts with another specified operand.

Cause: The user attempted to use two (or more) conflicting operands within the same statement.

Action: Remove one or both of the conflicting operands.

RMAN-06064: creating datafile fno=string name=string

RMAN-06064: creating datafile fno=string name=string

Cause: RESTORE or RECOVER command was issued and there were no backup available for the datafile.

Action: This is an informational message only.

RMAN-06063: DBID is not found in the recovery catalog

RMAN-06063: DBID is not found in the recovery catalog

Cause: DBID is not found in the recovery catalog.

Action: Verify that the DBID is correct and restart the command.

RMAN-06062: can not backup SPFILE because the instance was not started with SPFILE

RMAN-06062: can not backup SPFILE because the instance was not started with SPFILE

Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance.

Action: Create an SPFILE and re-start the instance using the SPFILE or modify the command.

RMAN-06061: WARNING: skipping archivelog compromises recoverability

RMAN-06061: WARNING: skipping archivelog compromises recoverability

Cause: SKIP INACCESSIBLE option resulted in skipping archivelogs during BACKUP. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log. This may occur because archived log was removed by an outside utility without updating the repository.

Action: If the archived log has been removed with an outside utility and the archivelog has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archivelog has not been previously backed up, then you should take a full backup of the database and archivelogs to preserve recoverability. Previous backups are not fully recoverable.

RMAN-06060: WARNING: skipping datafile compromises tablespace string recoverability

RMAN-06060: WARNING: skipping datafile compromises tablespace string recoverability

Cause: SKIP INACCESSIBLE or SKIP OFFLINE option resulted in skipping datafiles during BACKUP. If the datafile has in fact been lost and there is no backup, then the tablespace is no longer recoverable without ALL archive logs since datafile creation. This may occur because the datafile was deleted by an outside utility or the datafile is made OFFLINE (DROP(.

Action: If there is no backup of skipped datafiles and the tablespace has to be recoverable without ALL archive logs since datafile creation, then you should make these datafiles available for backup.

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability

Cause: The archived log was not found. The repository thinks it does exist. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log. This may occur because the archived log was removed by an outside utility without updating the repository.

Action: If the archived log has been removed with an outside utility and the archivelog has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archivelog has not been previously backed up, then you should take a full backup of the database and archivelogs to preserve recoverability. Previous backups are not fully recoverable.

RMAN-06058: a current control file cannot be included along with a standby control file

RMAN-06058: a current control file cannot be included along with a standby control file

Cause: standby controlfile was specified along with current controlfile .

Action: Remove standby controlfile or current controlfile from backup specification.

RMAN-06057: a standby control file cannot be included along with a current control file

RMAN-06057: a standby control file cannot be included along with a current control file

Cause: current controlfile was specified along with standby controlfile .

Action: Remove current controlfile or standby controlfile from backup specification.

RMAN-06056: could not access datafile number

RMAN-06056: could not access datafile number

Cause: A backup or copy could not proceed because the datafile header could not be read or the header was not valid.

Action: Make the datafile accessible or skip it.

RMAN-06055: could not find log sequence string thread string

RMAN-06055: could not find log sequence string thread string

Cause: A log which was on disk at the start of media recovery or which should have been restored from a backup set could not be found.

Action: Check the Recovery Manager message log to see if the log was restored by a previous job step. If so, then check the V$ARCHIVED_LOG view to see if the log is listed in the control file. If so, then validate that the log exists on disk and is readable. If the log was not restored, or was restored but no record of the log exists in V$ARCHIVED_LOG, then contact Oracle Customer Support.

RMAN-06054: media recovery requesting unknown log: thread string seq string lowscn string

RMAN-06054: media recovery requesting unknown log: thread string seq string lowscn string

Cause: Media recovery is requesting a log whose existance is not recorded in the recovery catalog or control file.

Action: If a copy of the log is available, then add it to the recovery catalog and or or control file via a CATALOG command and then retry the RECOVER command. If not, then a point in time recovery up to the missing log is the only alternative and database can be opened using ALTER DATABASE OPEN RESETLOGS command.

RMAN-06053: unable to perform media recovery because of missing log

RMAN-06053: unable to perform media recovery because of missing log

Cause: This message is accompanied with another message identifying the missing log. The log would be needed to perform the media recovery, but the log is not on disk and no backup set containing the log is available.

Action: Determine if a backup set containing the log can be made available. If so, then use the CHANGE command to make the backup set available and retry the command. If not, then a point in time recovery up to the missing log is the only alternative.

RMAN-06052: no parent backup or copy of datafile number found

RMAN-06052: no parent backup or copy of datafile number found

Cause: An incremental backup at level 1 or higher could not find any parent backup or copy of the indicated datafile. A level 0 backup of the datafile will be taken automatically.

Action: This is an informational message only.

RMAN-06051: DELETE INPUT option not implemented yet

RMAN-06051: DELETE INPUT option not implemented yet

Cause: This option was specified in a backup specification.

Action: Remove the DELETE INPUT option.

RMAN-06050: archive log thread number sequence number is already on disk as file string

RMAN-06050: archive log thread number sequence number is already on disk as file string

Cause: An archive log which was requested to be restored (either explicitely or via a range specification) does not need to be restored because it already exists on disk.

Action: None -this is an informational message

RMAN-06049: CHECK LOGICAL option not supported for archive log or current or standby control file copies

RMAN-06049: CHECK LOGICAL option not supported for archive log or current or standby control file copies

Cause: The check logical option was supplied but does not apply to this type of copy.

Action: Remove the CHECK LOGICAL operand and re-enter the command

RMAN-06048: duplicate control file specified for restoration from copy

RMAN-06048: duplicate control file specified for restoration from copy

Cause: The control file was specified more than once in the same RESTORE command.

Action: Correct and resubmit the RESTORE command.

RMAN-06047: duplicate datafile number specified for restoration from copy

RMAN-06047: duplicate datafile number specified for restoration from copy

Cause: The indicated datafile was specified more than once in the same restore command.

Action: Correct and resubmit the RESTORE command.

RMAN-06046: archive log name: string

RMAN-06046: archive log name: string

Cause: An error occurred while translating an archive log name to its recovery catalog recid or timestamp. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-06045: LEVEL option not supported for archive log or current or standby control file copies

RMAN-06045: LEVEL option not supported for archive log or current or standby control file copies

Cause: The LEVEL option was supplied but does not apply to this type of copy.

Action: Remove the LEVEL operand and re-enter the command.

RMAN-06043: TAG option not supported for archive log copies

RMAN-06043: TAG option not supported for archive log copies

Cause: The tag option was supplied but does not apply to this type of copy.

Action: Remove the TAG operand and re-enter the command

RMAN-06042: PLUS ARCHIVELOG option is not supported with non-datafile backups

RMAN-06042: PLUS ARCHIVELOG option is not supported with non-datafile backups

Cause: The PLUS ARCHIVELOG option was supplied but does not apply to this type of backup.

Action: Remove the PLUS ARCHIVELOG operand and re-enter the command.

RMAN-06041: cannot switch file number to copy of file number

RMAN-06041: cannot switch file number to copy of file number

Cause: An attempt was made to switch a datafile to a copy of a different datafile.

Action: Correct and resubmit the SWITCH command.

RMAN-06040: control file is already restored to file string

RMAN-06040: control file is already restored to file string

Cause: The best candidate control file for restoration is the one that is named in the RESTORE CONTROLFILE command, hence no action need be taken.

Action: None -this is an informational message.

RMAN-06039: no set newname command has been issued for datafile number

RMAN-06039: no set newname command has been issued for datafile number

Cause: A SWITCH command was specified for a datafile, but no destination was specified and no SET NEWNAME command has been previously issued for that file. An explicit file to switch to must be specified if no SET NEWNAME command has been issued.

Action: Correct and resubmit the SWITCH command.

RMAN-06038: recovery catalog package detected an error

RMAN-06038: recovery catalog package detected an error

Cause: A call to dbms_rcvman returned an error.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06036: datafile number is already restored to file string

RMAN-06036: datafile number is already restored to file string

Cause: A SET NEWNAME command was issued to restore a datafile to a location other than the original datafile, and Recovery Manager determined that the best candidate for restoring the file is the datafile copy with the same name, therefore the file is already restored and no action need be taken.

Action: None -this is an informational message.

RMAN-06035: wrong version of recover.bsq, expecting string, found string

RMAN-06035: wrong version of recover.bsq, expecting string, found string

Cause: The recover.bsq file is incompatible with the RMAN executable.

Action: Install the correct version of recover.bsq.

RMAN-06034: at least 1 channel must be allocated to execute this command

RMAN-06034: at least 1 channel must be allocated to execute this command

Cause: No channels were allocated.

Action: ALLOCATE a channel.

RMAN-06033: channel string not allocated

RMAN-06033: channel string not allocated

Cause: An rman command requests a specific channel, but the requested channel has not been allocated.

Action: ALLOCATE the channel, or correct the channel identifier.

RMAN-06032: at least 1 channel of TYPE DISK must be allocated to execute a COPY command

RMAN-06032: at least 1 channel of TYPE DISK must be allocated to execute a COPY command

Cause: No channel of TYPE DISK was allocated.

Action: Allocate a channel of TYPE DISK and re-issue the command.

RMAN-06031: could not translate database keyword

RMAN-06031: could not translate database keyword

Cause: An error was received when calling dbms_rcvman

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06030: the DELETE (ALL( INPUT option may not be used with a datafile backup set

RMAN-06030: the DELETE (ALL( INPUT option may not be used with a datafile backup set

Cause: The DELETE (ALL( INPUT option was specified for a backup that contains the current control file or datafiles.

Action: Remove the option and resubmit the command.

RMAN-06029: the control file may be included only in a datafile backup set

RMAN-06029: the control file may be included only in a datafile backup set

Cause: The include current or standby control file option was specified for an archive log backup set.

Action: Use this option only for datafile backup sets.

RMAN-06028: duplicate operand specified in restore specification: string

RMAN-06028: duplicate operand specified in restore specification: string

Cause: The CHANNEL, TAG, FROM, PARMS, VALIDATE, DEVICE TYPE, CHECK READONLY or DB_UNIQUE_NAME option was specified more than once in the restore command or in one of the restore specifications.

Action: Correct and resubmit the comand.

RMAN-06027: no archive logs found that match specification

RMAN-06027: no archive logs found that match specification

Cause: An archive log record specifier did not match any archive logs in the recovery catalog.

Action: Resubmit the command with a different archive log record specifier. The rman LIST command can be used to display all archive logs that Recovery Manager knows about.

RMAN-06026: some targets not found - aborting restore

RMAN-06026: some targets not found - aborting restore

Cause: Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged.

Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list.

RMAN-06025: no backup of log thread number seq number lowscn string found to restore

RMAN-06025: no backup of log thread number seq number lowscn string found to restore

Cause: An archive log restore restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user s restore operands.

Action: None -this is an informational message. See message 6026 for further details.

RMAN-06024: no backup or copy of the control file found to restore

RMAN-06024: no backup or copy of the control file found to restore

Cause: A control file restore could not proceed because no backup or copy of the control file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user s restore operands.

Action: None -this is an informational message. See message 6026 for further details.

RMAN-06023: no backup or copy of datafile number found to restore

RMAN-06023: no backup or copy of datafile number found to restore

Cause: A datafile, tablespace, or database restore could not proceed because no backup or copy of the indicated file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user s restore operands.

Action: None -this is an informational message. See message 6026 for further details.

RMAN-06022: invalid level specified for image copy: number

RMAN-06022: invalid level specified for image copy: number

Cause: An invalid incremental backup level was specified for an image copy.

Action: Incremental backup level must be 0 for image copies.

RMAN-06021: FROM DATAFILECCOPY or BACKUPSET may not be specified with archive logs

RMAN-06021: FROM DATAFILECCOPY or BACKUPSET may not be specified with archive logs

Cause: The FROM DATAFILECCOPY or BACKUPSET option applies only to datafile and control file restores.

Action: Use this option only for datafile and control file restores.

RMAN-06020: connected to auxiliary database (not started)

RMAN-06020: connected to auxiliary database (not started)

Cause: This is an informational message only.

Action: No action is required.

RMAN-06019: could not translate tablespace name string

RMAN-06019: could not translate tablespace name string

Cause: An error occurred while looking up the specified tablespace name in the recovery catalog or target database control file.

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the tablespace is entered correctly. If the tablespace was added recently, then a RESYNC CATALOG must be done to update the recovery catalog.

RMAN-06018: duplicate operand specified in backup specification: string

RMAN-06018: duplicate operand specified in backup specification: string

Cause: A backup specification operand appears more than once in a backup specification.

Action: Delete the duplicate operand.

RMAN-06017: initialization of parser failed

RMAN-06017: initialization of parser failed

Cause: The parser package initialization routine returned an error.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-06016: duplicate backup operand specified: string

RMAN-06016: duplicate backup operand specified: string

Cause: The specified operand appears more than once in the same backup specifier or backup command.

Action: Delete the duplicated operand.

RMAN-06015: error while looking up datafile copy name: string

RMAN-06015: error while looking up datafile copy name: string

Cause: An error occurred while looking up the specified datafile copy name in the recovery catalog or target database control file.

Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the filename is entered correctly. If the datafilevopy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog.

OCI-31033: Requested number of XML children string exceeds maximum string

OCI-31033: Requested number of XML children string exceeds maximum string

Cause: An attempt was made to add more than the maximum number of allowable children in an XML element.

Action: Redefine the schema to allow breaking up of the children among siblings.

OCI-31030: Unable to retrieve XML document

OCI-31030: Unable to retrieve XML document

Cause: The resource had an invalid (dangling) REF to an XML document.

Action: Rebind the resource using a valid XMLType REF.

OCI-31029: Cannot bind to unsaved resource

OCI-31029: Cannot bind to unsaved resource

Cause: An attempt was made to bind to a resource that had not been saved to disk.

Action: Bind only to saved resources.

OCI-31028: Resource metadata length string exceeded maximum length string

OCI-31028: Resource metadata length string exceeded maximum length string

Cause: An attempt was made to insert resource metadata that exceeded the maximum length of that type of metadata.

Action: Keep resource metadata within its allowed length.

OCI-31027: Path name or handle string does not point to a resource

OCI-31027: Path name or handle string does not point to a resource

Cause: An attempt was made to retrieve a resource based on a path name or resource handle that points to an entity other than a resource.

Action: Do not attempt to retrieve a resource based on that path name or resource handle.

OCI-31025: Invalid document element

OCI-31025: Invalid document element

Cause: An attempt was made to replace the data at an invalid index number in the XML document

Action: Supply a correct occurrence number and try again.

OCI-31023: Index size error

OCI-31023: Index size error

Cause: The index is greater than the allowed value.

Action: Make sure the index is less than allowed value.

OCI-31022: Element not found

OCI-31022: Element not found

Cause: The element was not found.

Action: Make sure the specified element exists.

OCI-31021: Element definition not found

OCI-31021: Element definition not found

Cause: The element definition was not found.

Action: Supply the definition for the element or use a defined element.

OCI-31020: The operation is not allowed, Reason: string

OCI-31020: The operation is not allowed, Reason: string

Cause: The operation attempted is not allowed

Action: See reason and change to a valid operation.

OCI-31019: Recursive deletion snapshot too old for string or string

OCI-31019: Recursive deletion snapshot too old for string or string

Cause: Changes were made to the structure of a directory while it was being recursively deleted.

Action: Try deleting the directory again.

OCI-31018: Error deleting XML document

OCI-31018: Error deleting XML document

Cause: The XMLType object pointed to by the given REF could not be deleted because either the REF was invalid or it pointed to a non-existent table.

Action: Either use FORCE deletion or supply a valid REF.

OCI-31017: Error generating unique OID for XML document

OCI-31017: Error generating unique OID for XML document

Cause: An error occurred while generating a globally unique OID for storing an XML document.

Action: none

OCI-31016: Attempted to delete entry without name

OCI-31016: Attempted to delete entry without name

Cause: An attempt was made to delete an entry from the hierarchical resolver without a child name.

Action: Supply a child name and try deleting again.

OCI-31015: Attempted to insert entry without name

OCI-31015: Attempted to insert entry without name

Cause: An attempt was made to insert an entry into the hierarchical resolver without a child name.

Action: Supply a child name and try inserting again.

OCI-31014: Attempted to delete the root container

OCI-31014: Attempted to delete the root container

Cause: An attempt was made to delete the root container in the hierarchical index.

Action: Do not delete the root container.

OCI-31013: Invalid XPATH expression

OCI-31013: Invalid XPATH expression

Cause: XPATH expression passed to the function is invalid.

Action: Check the xpath expression for possible syntax errors.

OCI-31012: Given XPATH expression not supported

OCI-31012: Given XPATH expression not supported

Cause: XPATH expression passed to the function is currently unsupported.

Action: Check the xpath expression and change it to use a supported expression.

OCI-31011: XML parsing failed

OCI-31011: XML parsing failed

Cause: XML parser returned an error while trying to parse the document.

Action: Check if the document to be parsed is valid.

OCI-31010: XML element index string exceeds maximum insertion index string

OCI-31010: XML element index string exceeds maximum insertion index string

Cause: An attempt was made to insert an XML element at an invalid index location in the node.

Action: Choose a new index that falls within the allowed range.

OCI-31009: Access denied for property string

OCI-31009: Access denied for property string

Cause: An attempt was made to access a property you don t have access to

Action: Check the ACL to see what privileges you have for this property

OCI-31007: Attempted to delete non-empty container string or string

OCI-31007: Attempted to delete non-empty container string or string

Cause: An attempt was made to delete a non-empty container in the XDB hierarchical resolver.

Action: Either perform a recursive deletion, or first delete the contents of the container.

OCI-31006: Path name segment length string exceeds maximum length string

OCI-31006: Path name segment length string exceeds maximum length string

Cause: The length of a path name segment passed to the XDB hierarchical resolver exceeded the maximum length of a path name segment.

Action: Choose a shorter path name segment.

OCI-31005: Path name length string exceeds maximum length string

OCI-31005: Path name length string exceeds maximum length string

Cause: The length of a path name passed to the XDB hierarchical resolver exceeded the maximum length.

Action: Choose a shorter path name.

OCI-31004: Length string of the BLOB in XDB$H_INDEX is below the minimum string

OCI-31004: Length string of the BLOB in XDB$H_INDEX is below the minimum string

Cause: In the XDB$H_INDEX table, the CHILDREN column, a BLOB, must have a certain minimum length without being chained. The calculated length of the LOB was less than the stated minimum.

Action: Set the value of the init.ora parameter db_block_size to at least 2K. For XDB to run at its fastest, set db_block_size to 8K.

OCI-31003: Parent string already contains child entry string

OCI-31003: Parent string already contains child entry string

Cause: An attempt was made to insert a duplicate child into the XDB hierarchical resolver.

Action: Insert a unique name into the container.

OCI-31002: Path name string is not a container

OCI-31002: Path name string is not a container

Cause: XDB expected the given path name to represent a container.

Action: Pass a path name or resource handle that represents a container.

OCI-31001: Invalid resource handle or path name string

OCI-31001: Invalid resource handle or path name string

Cause: An invalid resource handle or path name was passed to the XDB hierarchical resolver.

Action: Pass a valid resouce handle or path name to the hierarchical resolver.

OCI-31000: Resource string is not an XDB schema document

OCI-31000: Resource string is not an XDB schema document

Cause: The given schema URL does not refer to a registered XDB schema

Action: Make sure the specified schema has been registered in XDB

OCI-30991: cannot use DOM to add special attribute to schema-based parent

OCI-30991: cannot use DOM to add special attribute to schema-based parent

Cause: An attempt was made to add or remove an xsi:schemaLocation, xsi:noNamespaceSchemaLocation, xsi:type, or xsi:nil attribute to or from a schema-based XML node using DOM.

Action: Use the updateXML operator instead of DOM.

OCI-30990: insufficient privileges to change owner of resource string

OCI-30990: insufficient privileges to change owner of resource string

Cause: An attempt was made to change the lamp;lt;lamp;nbsp;Ownerlamp;gt; field of an XML DB resource without sufficient privileges to do so.

Action: Switch to SYS before performing the ownership change, or have the intended recipient of the resource perform the transfer.

RMAN-01009: syntax error: found string : expecting one of: string

RMAN-01009: syntax error: found string : expecting one of: string

Cause: A syntax error was signalled during parsing.

Action: Correct the input.

RMAN-01008: the bad identifier was: string

RMAN-01008: the bad identifier was: string

Cause: This is an informational message indicating the identifier token that caused a syntax error.

Action: No action is required.

RMAN-01007: at line number column number file: string

RMAN-01007: at line number column number file: string

Cause: This is an informational message indicating the line and column where a syntax error was detected.

Action: No action is required.

RMAN-01006: error signalled during parse

RMAN-01006: error signalled during parse

Cause: An error was signalled during parsing.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-00703: The cmdfile has no syntax errors

RMAN-00703: The cmdfile has no syntax errors

Cause: This is an informational message only.

Action: No action is required.

RMAN-00702: The command has no syntax errors

RMAN-00702: The command has no syntax errors

Cause: This is an informational message only.

Action: No action is required.

RMAN-00701: SCRIPT requires that CATALOG be specified on the command line

RMAN-00701: SCRIPT requires that CATALOG be specified on the command line

Cause: A SCRIPT option was included on the RMAN command line without a specified CATALOG recovery catalog.

Action: Specify the CATALOG option on the RMAN command line.

RMAN-00700: SCRIPT requires that TARGET be specified on the command line

RMAN-00700: SCRIPT requires that TARGET be specified on the command line

Cause: A SCRIPT option was included on the RMAN command line without a specified TARGET database.

Action: Specify the TARGET option on the RMAN command line.

RMAN-00601: fatal error in recovery manager

RMAN-00601: fatal error in recovery manager

Cause: A fatal error has occurred.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-00600: internal error, arguments (string( (string( (string( (string( (string(

RMAN-00600: internal error, arguments (string( (string( (string( (string( (string(

Cause: An internal error in recovery manager occurred.

Action: Contact Oracle Customer Support.

RMAN-00579: SCRIPT cannot be used with CMDFILE

RMAN-00579: SCRIPT cannot be used with CMDFILE

Cause: The SCRIPT and CMDFILE options cannot be used together. When using the SCRIPT option, RMAN executes only the specified script.

Action: Remove either the SCRIPT or CMDFILE option.

RMAN-00578: pipe string is not private and owned by SYS

RMAN-00578: pipe string is not private and owned by SYS

Cause: The pipe that RMAN needs to use for its input or output is either a public pipe or a private pipe that is not owned by SYS. This is a potential security problem, because it allows a non-SYS user to issue commands to RMAN or to retrieve the RMAN output.

Action: If you are attempting to put data on the RMAN input pipe prior to starting RMAN, so RMAN will process the data on the pipe as soon as it starts, you must be connected as SYS and you must first use the dbms_pipe.create_pipe function to explicitely create the pipe as a private pipe.

RMAN-00577: PIPE requires that TARGET be specified on the command line

RMAN-00577: PIPE requires that TARGET be specified on the command line

Cause: The PIPE option obtains its input from, and writes its output to, an Oracle database pipe in the target database. Therefore, the target database connection must be specified on the command line, so that RMAN can connect to the target database to receive its input from the pipe.

Action: Specify the TARGET option on the RMAN command line.

RMAN-00576: PIPE cannot be used with CMDFILE

RMAN-00576: PIPE cannot be used with CMDFILE

Cause: The PIPE and CMDFILE options cannot be used together. When using the PIPE option, RMAN must obtain its input from the input pipe.

Action: Remove either the PIPE or CMDFILE option.

RMAN-00575: timeout while trying to write to dbms_pipe

RMAN-00575: timeout while trying to write to dbms_pipe

Cause: d by death of the process that was talking to rman.

Action: RMAN will abort.

RMAN-00574: rman aborting due to errors read or writing dbms_pipe

RMAN-00574: rman aborting due to errors read or writing dbms_pipe

Cause: RMAN was run with input or output being sent to dbms_pipe. An error was encountered while reading from or writing to the pipe. This error should be preceeded by information describing the error.

Action: RMAN terminates. Refer to the cause or action for the preceding errors.

RMAN-00573: dbms_pipe.next_item_time returned unknown type code: number

RMAN-00573: dbms_pipe.next_item_time returned unknown type code: number

Cause: This is an internal error

Action: contact Oracle Customer Support.

RMAN-00572: waiting for dbms_pipe input

RMAN-00572: waiting for dbms_pipe input

Cause: This message is used only when the PIPE option was specified.

Action: enqueue some RMAN input into the pipe

RMAN-00571: ===========================================================

RMAN-00571: ===========================================================

Cause: Displayed to highlight the error message stack.

Action: The errors are printed in last-in first-out order. So to interpret them correctly, read from the bottom to the top.

RMAN-00570: **end-of-file**

RMAN-00570: **end-of-file**

Cause: The end of an inline cmdfile was reached. This is just an informational message.

Action: No action is required.

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

Cause: This message preceeds an error message stack.

Action: The errors are printed in last-in first-out order. So to interpret them correctly, read from the bottom to the top.

RMAN-00568: user interrupt received

RMAN-00568: user interrupt received

Cause: The user typed ^C or ATTN.

Action: No action is required.

RMAN-00567: Recovery Manager could not print some error messages

RMAN-00567: Recovery Manager could not print some error messages

Cause: An error occurred while trying to print the error message stack.

Action: If the associated error message indicates a condition that can be corrected, do so, otherwise contact Oracle.

RMAN-00566: could not open TRACE string

RMAN-00566: could not open TRACE string

Cause: An error occurred when trying to open the file.

Action: Check that the filename was specified correctly and that the user running RMAN has write permission for the file.

RMAN-00565: unable to read input file

RMAN-00565: unable to read input file

Cause: An error occurred while trying to read from STDIN or from the CMDFILE.

Action: Ensure that the cmdfile is readable. The cmdfile must be a text file with 1 line per record.

RMAN-00564: host data too long

RMAN-00564: host data too long

Cause: The SQL*NET host connect string exceeds the maximum allowable length.

Action: Correct the host string.

RMAN-00563: password too long

RMAN-00563: password too long

Cause: The specified password exceeds the maximum allowable password length.

Action: Correct the password.

RMAN-00562: username too long

RMAN-00562: username too long

Cause: The specified user name exceeds the maximum allowable username length.

Action: Correct the username.

RMAN-00558: error encountered while parsing input commands

RMAN-00558: error encountered while parsing input commands

Cause: The parser detected a syntax error.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-00557: could not open MSGLOG string

RMAN-00557: could not open MSGLOG string

Cause: An error occurred when trying to open the file.

Action: Check that the filename was specified correctly and that the file exists and that the user running RMAN has write permission for the file.

RMAN-00556: could not open CMDFILE string

RMAN-00556: could not open CMDFILE string

Cause: An error occurred when trying to open the file.

Action: Check that the filename was specified correctly and that the file exists and that the user running RMAN has read permission for the file.

RMAN-00555: target database connect string must be specified

RMAN-00555: target database connect string must be specified

Cause: The TARGET parameter was not specified.

Action: Supply the necessary parameter.

RMAN-00554: initialization of internal recovery manager package failed

RMAN-00554: initialization of internal recovery manager package failed

Cause: The internal package initialization routine returned an error.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-00553: internal recovery manager package failed to load

RMAN-00553: internal recovery manager package failed to load

Cause: lpmloadpkg() return an error indication.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-00552: syntax error in command line arguments

RMAN-00552: syntax error in command line arguments

Cause: The arguments supplied to RMAN could not be parsed, or no arguments were supplied at all.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-00551: initialization of parser package failed

RMAN-00551: initialization of parser package failed

Cause: The parser package initialization routine returned an error.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

RMAN-00550: parser package failed to load

RMAN-00550: parser package failed to load

Cause: lpmloadpkg() return an error indication.

Action: This message should be accompanied by other error message(s) indicating the cause of the error.

OCI-31199: Warning in processing file string

OCI-31199: Warning in processing file string

Cause: A warning was raised while operating on the specifed file. However, the current operation was completed successfully.

Action: This is primarily an informational message. Look at the next error on the stack to obtain further information.

OCI-31198: Mismatch in number of bytes transferred due to non-binary mode

OCI-31198: Mismatch in number of bytes transferred due to non-binary mode

Cause: An error occurred while reading the specifed file. The most probable cause is that the transfer was initiated in ASCII mode.

Action: Ensure that the transfer mode is set to BINARY

OCI-31197: Error in processing file string

OCI-31197: Error in processing file string

Cause: An error occurred while operating on the specifed file. The possible causes are the file header is corrupt or check the next error on stack

Action: Ensure that the specified file is correct. Look at the next error on the stack and take appropriate action.

OCI-31196: XML nodes over string in size cannot be printed

OCI-31196: XML nodes over string in size cannot be printed

Cause: An attempt was made to use an XML Text Node with a size greater than 64K, or an XML Comment Node with a size greater than 4K. These cannot be printed. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.

Action: Use getClobVal() or getStringVal() to print the Document.

OCI-31195: XML node string (type=string) does not support this operation

OCI-31195: XML node string (type=string) does not support this operation

Cause: The given node s type is not supported for this operation. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.

Action: Use a valid node type for the operation.

OCI-31194: Resource string is already deleted

OCI-31194: Resource string is already deleted

Cause: Access a version-controlled resource that is already deleted.

Action: Remove the cyclic definitions in the type and retry compilation.

OCI-31193: This versioning feature isn t supported for resource string

OCI-31193: This versioning feature isn t supported for resource string

Cause: Either one of the following is the cause:

Action: Avoid using these features.

OCI-31192: Resource string has not been checked out

OCI-31192: Resource string has not been checked out

Cause: Either one of the following is the cause: to the workspace by any user in a workspace

Action: checked in the resource from the workspace before checking out

OCI-31191: Resource string is already checked out

OCI-31191: Resource string is already checked out

Cause: Either one of the following is the cause: by the same of different user.

Action: checked in the resource from the workspace before checking out

OCI-31190: Resource string is not a version-controlled resource

OCI-31190: Resource string is not a version-controlled resource

Cause: Either one of the following is the cause: - Checkout is requested for a resource that isn t under version control . Only version-controlled resource can be checked out.

Action: put the resource under version-control before checking out.

OCI-31185: DOM Nodes do not belong to the same DOM Document

OCI-31185: DOM Nodes do not belong to the same DOM Document

Cause: The specified PL or SQL DOM Node does not belong to the parent DOM Document of the referring DOM Node.

Action: Ensure that both the DOM Nodes are part of the same DOM Document.

OCI-31182: Too many PL or SQL DOM handles specified

OCI-31182: Too many PL or SQL DOM handles specified

Cause: An attempt was made to create a PL or SQL DOM handle that exceeded the maximum allowable number of PL or SQL DOM handles.

Action: Free PL or SQL DOM handles and try the operation again.

OCI-31181: PL or SQL DOM handle accesses node that is no longer available

OCI-31181: PL or SQL DOM handle accesses node that is no longer available

Cause: The specified pl or sql handle is referencing a node in a DOM Document that is no longer available.

Action: Ensure that the pl or sql handle for the target node is valid and try the operation again.

OCI-31180: DOM Type mismatch in invalid PL or SQL DOM handle

OCI-31180: DOM Type mismatch in invalid PL or SQL DOM handle

Cause: The specified PL or SQL DOM handle is referencing a DOM Node whose DOM Type that does not match the one available in the session. This could happen because the pl or sql handle was reused, or the original document is no longer available.

Action: Ensure that the pl or sql handle for the target node is valid and try the operation again.

OCI-31168: Node localname and namespace values should be less than 64K

OCI-31168: Node localname and namespace values should be less than 64K

Cause: An attempt was made to specify an XML Node with localname or namespace value greater than or equal to 64K. This is not supported.

Action: Node localnames and namespace values should be under 64K. or or or or or or 31180 - 31189 reserved for PL or SQL DOM API

OCI-31167: XML nodes over 64K in size cannot be inserted

OCI-31167: XML nodes over 64K in size cannot be inserted

Cause: An attempt was made to insert an XML Text Node with a size greater than 64K. This is not supported.

Action: Create text nodes under 64K.

OCI-31165: cannot load object-relational XML attribute using direct path

OCI-31165: cannot load object-relational XML attribute using direct path

Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column either contains an out-of-line partitioned table or the table itself is partitioned by one of the attributes of xmltype. This type of table cannot be loaded with direct path.

Action: Perform the load with conventional path mode.

OCI-31164: cannot load object-relational XML attribute using direct path

OCI-31164: cannot load object-relational XML attribute using direct path

Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column contains a type with subtypes. This type of attribute cannot be loaded with direct path.

Action: Perform the load with conventional path mode.

OCI-31163: element or attribute string has invalid attribute value string (should be string )

OCI-31163: element or attribute string has invalid attribute value string (should be string )

Cause: An element or attribute for a complextype derived by restriction has an attribute whose value is different from that in the base type

Action: Remove the mismatched attribute values from the offending element or attribute

OCI-31162: element or attribute string has no SQLType specified

OCI-31162: element or attribute string has no SQLType specified

Cause: Schema registration was invoked with GENTYPES=false without specifying a SQLType for some element or attribute

Action: Specify a SQLType for the offending element or attribute and register the schema again

OCI-31161: element or attribute string cannot be stored out of line

OCI-31161: element or attribute string cannot be stored out of line

Cause: An element or attribute of a simple type has SQLInline=false

Action: Remove the SQLInline=false qualification for the offending element or attribute

OCI-31160: max substitution group size string exceeded by string (string) for head element string (string)

OCI-31160: max substitution group size string exceeded by string (string) for head element string (string)

Cause: The maximum limit on nested substitution groups has been exceeded by an element.

Action: Delete specified schema and re-register it after removing the offending substitution element.

OCI-31159: XML DB is in an invalid state

OCI-31159: XML DB is in an invalid state

Cause: XML DB s internal tables are in an invalid state, probably because the database was not upgraded or the upgrade was not successful

Action: Ensure that the database is upgraded successfully. If the problem persists, contact Oracle Support

OCI-31158: schema string currently being referenced

OCI-31158: schema string currently being referenced

Cause: The specified schema URL is currently being referenced by the same session. This could happen because of PLSQL XMLType variables still in scope.

Action: Ensure all references to this schema in this session are released and try the operation again.

OCI-31157: Invalid Content-Type charset

OCI-31157: Invalid Content-Type charset

Cause: HTTP Content-Type header had a charset that Oracle does not understand.

Action: Fix the Content-Type header in the HTTP request.

OCI-31155: attribute string not in XDB namespace

OCI-31155: attribute string not in XDB namespace

Cause: The specified attribute should be prefixed with XDB s namespace.

Action: Ensure that all XDB specified attributes are prefixed with XDB s namespace and try again.

OCI-31154: invalid XML document

OCI-31154: invalid XML document

Cause: The XML document is invalid with respect to its XML Schema.

Action: Fix the errors identified and try again.

OCI-31153: Cannot create schema URL with reserved prefix http: or or xmlns.oracle.com or xdb or schemas or

OCI-31153: Cannot create schema URL with reserved prefix http: or or xmlns.oracle.com or xdb or schemas or

Cause: This prefix is reserved for XDB extended schema URLs and cannot be used in a user specified URL.

Action: Modify the prefix to a different one.

OCI-31151: Cyclic definition encountered for string: string

OCI-31151: Cyclic definition encountered for string: string

Cause: The schema definition for this type has cycles.

Action: Remove cyclic definition and re-compile schema.

OCI-31122: The string operator has incorrect RHS value

OCI-31122: The string operator has incorrect RHS value

Cause: The right hand side value that has been specified for the operator does not evaluate to TRUE

Action: Specify value on the right hand side that evaluate to TRUE or or or or or or 31151 - 31189 reserved for XML Schema Compiler

OCI-31121: The string operator can not be FALSE

OCI-31121: The string operator can not be FALSE

Cause: The value of the operator that is specified is FALSE

Action: Specify an operator that evaluates to TRUE

OCI-31116: Tablespace not specified correctly

OCI-31116: Tablespace not specified correctly

Cause: XDB cannot be moved to the specified tablespace.

Action: Specify a valid tablespace.

OCI-31115: XDB configuration error: string

OCI-31115: XDB configuration error: string

Cause: An error related to XDB configuration has occurred.

Action: Make sure the configuration resource contains valid data.

OCI-31114: XDB configuration has been deleted or is corrupted

OCI-31114: XDB configuration has been deleted or is corrupted

Cause: The XDB configuration resource has been deleted or corrupted.

Action: Reinstall XDB, or reinsert a valid configuration document.

OCI-31112: fail to string for string port using xdb configuration

OCI-31112: fail to string for string port using xdb configuration

Cause: port number for the defined presentation is not valid

Action: Either the port number is already in use or it is protected. Specify another port number.

OCI-31111: table string cannot be hierarchically enabled

OCI-31111: table string cannot be hierarchically enabled

Cause: Trigger lamp;lt;lamp;nbsp;tabnamelamp;gt;_xdb_pitrigger already exists

Action: Delete all rows in the hierarchical index and then rebuild it.

OCI-31105: User does not own lock string

OCI-31105: User does not own lock string

Cause: The lock to be unlocked is not owned by the user.

Action: none

OCI-31104: Cannot find lock with token string on string for unlock

OCI-31104: Cannot find lock with token string on string for unlock

Cause: The lock may have been unlock or it may have expired.

Action: No action needed. Unlock already successful.

OCI-31103: Resource locked in shared mode. Cannot add exclusive lock

OCI-31103: Resource locked in shared mode. Cannot add exclusive lock

Cause: The resource is locked in shared mode. Cannot add a shared lock.

Action: Try locking in shared mode or unlocking the existing lock.

OCI-31102: Already locked in exclusive mode. Cannot add lock.

OCI-31102: Already locked in exclusive mode. Cannot add lock.

Cause: The resource is already locked in exclusive mode. Cannot add another lock.

Action: Unlock the existing lock.

OCI-31101: Token string not given while locking resource string

OCI-31101: Token string not given while locking resource string

Cause: Locking attempted on resource when the pricipal already owns a lock given by the token above.

Action: Reattempt the lock with the token.

OCI-31100: XDB Locking Internal Error

OCI-31100: XDB Locking Internal Error

Cause: An XDB Locking Internal error has occurred.

Action: Contact Oracle Support.

OCI-31099: XDB Security Internal Error

OCI-31099: XDB Security Internal Error

Cause: An XDB Security internal error has occurred.

Action: Contact Oracle Support. or or or or or or 31100 - 31110 reserved for WebDAV compliant resource locks

OCI-31097: Hierarchical Index not empty

OCI-31097: Hierarchical Index not empty

Cause: An attempt was made to rebuild the hierarchical index which is not empty.

Action: Delete all rows in the hierarchical index and then rebuild it.

OCI-31096: validation failed for schema

OCI-31096: validation failed for schema

Cause: The XML Schema could not be validated.

Action: Make sure that the SQLType and other datatype mapping is valid.

OCI-31095: cannot generate string : string.string already exists

OCI-31095: cannot generate string : string.string already exists

Cause: The type or table name specified in the XML schema document cannot be generated because it is already being used.

Action: Use different names for types or tables or use the NOGEN mode so that schema compiler does not generate new types or tables.

OCI-31094: incompatible SQL type string for attribute or element string

OCI-31094: incompatible SQL type string for attribute or element string

Cause: The SQL type information provided in the XML schema is not compatible with the XML datatype for the specified attribute or element.

Action: Make sure that the specified SQL types are compatible with the declared XML datatypes.

OCI-31093: null or invalid value specified for parameter : string

OCI-31093: null or invalid value specified for parameter : string

Cause: The argument value passed for the given parameter is null or invalid.

Action: Make sure that all the input argument values are valid.

OCI-31092: invalid SQL name string

OCI-31092: invalid SQL name string

Cause: The XML schema document contains an invalid SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.

Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. This implies that the database length and other restrictions on names be satisfied.

OCI-31091: empty string specified as a SQL name

OCI-31091: empty string specified as a SQL name

Cause: The XML schema document contains a null SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.

Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. Otherwise, remove such attributes from the schema and try again.

OCI-31090: invalid database schema name string

OCI-31090: invalid database schema name string

Cause: The XML schema document contains an invalid database schema name For example, the value of attribute SQLSchema

Action: Make sure that all database user or schema names specified in the XML schema document refer to existing database users or schemas.

OCI-31089: schema string does not target namespace string

OCI-31089: schema string does not target namespace string

Cause: The schema document contains references (via include and import definitions) to other schemas that do not belong to valid namespaces.

Action: Make sure that all schemas referenced via include definitions target the same namespace as the parent schema. Further make sure that the namespace specified in the import definition matches the actual target namespace of the specified schema.

OCI-31088: object string . string depends on the schema

OCI-31088: object string . string depends on the schema

Cause: An attempt was made to delete a schema which has dependent objects.

Action: Either drop the dependent objects prior to deleting the schema or use the CASCADE or FORCE options.

OCI-31087: insufficient privileges to delete schema string

OCI-31087: insufficient privileges to delete schema string

Cause: An attempt was made to delete a schema resource without sufficient privileges.

Action: Make sure that the user has sufficient privileges to delete the schema.

OCI-31086: insufficient privileges to register global schema string

OCI-31086: insufficient privileges to register global schema string

Cause: An attempt was made to register a global schema without sufficient privileges.

Action: Make sure that the user has sufficient privileges to register a global schema.

OCI-31085: schema string already registered

OCI-31085: schema string already registered

Cause: An attempt was made to register a schema with the same URL as a previously registered schema.

Action: Register the schema with a different URL.

OCI-31084: error while creating table string . string for element string

OCI-31084: error while creating table string . string for element string

Cause: An error occurred while trying to create the table based on the declaration for the identified element.

Action: Fix the identified error and try again.

OCI-31083: error while creating SQL type string . string

OCI-31083: error while creating SQL type string . string

Cause: An error occurred while trying to create the SQL type based on the specification of a complex type.

Action: Fix the identified error and try again.

OCI-31082: invalid attribute string specified in declaration of string

OCI-31082: invalid attribute string specified in declaration of string

Cause: The XML schema specifies an invalid attribute.

Action: Remove specification of the invalid attribute.

OCI-31081: name not specified for global declaration

OCI-31081: name not specified for global declaration

Cause: The XML schema does not specify the name for the global declaration of attribute or element or simpleType or complexType.

Action: Specify names for all global declarations.

OCI-31080: type not specified for attribute or element string

OCI-31080: type not specified for attribute or element string

Cause: The identified attribute or element does not have a type.

Action: Make sure that every attribute and element has a valid type specification.

OCI-31079: unable to resolve reference to string string

OCI-31079: unable to resolve reference to string string

Cause: The identified type or attribute or element could not be resolved.

Action: Make sure that the name corresponds to a valid XML (simple or complex) type or attribute or element and try again.

OCI-31078: error in SQL mapping information

OCI-31078: error in SQL mapping information

Cause: There is an error in the SQL type and table specification within the XML Schema.

Action: Ensure that all specified SQL types and tables are valid and compatible with the corresponding XML types.

OCI-31077: invalid attribute string specified

OCI-31077: invalid attribute string specified

Cause: The XML schema specifies an invalid attribute.

Action: Remove specification of the invalid attribute.

OCI-31076: required attribute string not specified

OCI-31076: required attribute string not specified

Cause: The XML schema does not specify a required attribute.

Action: Specify a value for the required attribute.

OCI-31075: invalid string declaration in XML Schema

OCI-31075: invalid string declaration in XML Schema

Cause: The XML schema contains an invalid declaration identified by the message.

Action: Fix the identified error and try again.

OCI-31073: Resource not retrieved using path name

OCI-31073: Resource not retrieved using path name

Cause: An attempt was made to access the path name of a resource that was either never saved to disk or was loaded using a method other than with its path name.

Action: Perform path name operations only on resources obtained using a path name. or or or or or or 31075 - 31099 reserved for XML Schema Compiler

OCI-31072: Too many child nodes in XMLType fragment for updateXML

OCI-31072: Too many child nodes in XMLType fragment for updateXML

Cause: An attempt was made to pass an XMLType fragment with multiple children as new data for the updateXML operator.

Action: Extract the desired child from the XMLType before passing it to updateXML as the desired new XML node.

OCI-31071: Invalid database username or GUID string

OCI-31071: Invalid database username or GUID string

Cause: An attempt was made to set an invalid username or GUID into an XDB resource metadata property.

Action: Verify the validity of the username or GUID and try again.

OCI-31070: Invalid database user ID string

OCI-31070: Invalid database user ID string

Cause: An attempt was made set an invalid user ID into an XDB resource metadata property.

Action: Verify the validity of the user ID and try again.

OCI-31069: Cannot apply typed changes to non-schema-based XMLType nodes

OCI-31069: Cannot apply typed changes to non-schema-based XMLType nodes

Cause: An attempt was made to insert, delete, or update a non-schema-based XMLType node using an XML schema definition.

Action: Make changes to non-typed nodes only by referencing their tag names.

OCI-31068: updateXML expected data format (string( instead of (string(

OCI-31068: updateXML expected data format (string( instead of (string(

Cause: An attempt was made to use updateXML to update data with a node of the incorrect type. Text and attribute nodes must be updated with string data, whereas element nodes must be updated with XMLType data.

Action: Use CREATEXML or getStringVal to coerce the new data to the proper format.

OCI-31067: XML nodes must be updated with nodes of the same type

OCI-31067: XML nodes must be updated with nodes of the same type

Cause: An attempt was made to use updateXML to update an XML node with a node of another type.

Action: Ensure that the node specified by the XPath matches the type of new data provided.

OCI-31066: Insertion of string into string creates a cycle

OCI-31066: Insertion of string into string creates a cycle

Cause: An attempt was made to insert a link into the XDB hierarchy that would create a cycle in the tree.

Action: Ensure that links to existing resources do not cause cycles.

OCI-31065: Cannot modify read-only property (string(

OCI-31065: Cannot modify read-only property (string(

Cause: An attempt was made to modify an immutable XML node.

Action: Use only read operations on such properties.

OCI-31062: Cannot delete an unsaved resource

OCI-31062: Cannot delete an unsaved resource

Cause: An attempt was made to delete a resource that had not been saved to disk.

Action: Delete only saved resources.

OCI-31060: Resource at path string could not be deleted

OCI-31060: Resource at path string could not be deleted

Cause: An error occurred while deleting the named resource. The specific error can be found one lower on the error stack.

Action: Look at the next error on the stack and take approprate action.

OCI-31059: Cannot insert root XML document node if it already exists

OCI-31059: Cannot insert root XML document node if it already exists

Cause: An attempt was made to insert a root node into an XML document that already had a root node.

Action: Call the appropriate replace function to replace the node instead of inserting it anew.

OCI-31058: cannot modify read-only XOBs

OCI-31058: cannot modify read-only XOBs

Cause: Read-Only XOBs cannot be modified.

Action: Use only read operations on such a XOB.

OCI-31057: Display Name of the element being inserted is null

OCI-31057: Display Name of the element being inserted is null

Cause: The Display Name of the element which is being inserted into the RESOURCE_VIEW is null

Action: Specify the Display Name and insert the element into RESOURCE_VIEW

OCI-31056: The document being inserted does not conform to string

OCI-31056: The document being inserted does not conform to string

Cause: The XMLType element being inserted into the RESOURCE_VIEW does not conform to the specified Schema

Action: Insert an element which conforms to the specified Schema

OCI-31055: A null XMLType element cannot be inserted into RESOURCE_VIEW

OCI-31055: A null XMLType element cannot be inserted into RESOURCE_VIEW

Cause: The element which is being inserted into the RESOURCE_VIEW is NULL

Action: Specify a non-null XMLType element to insert into RESOURCE_VIEW

OCI-31054: The string operator cannot have an ancillary operator

OCI-31054: The string operator cannot have an ancillary operator

Cause: An ancillary operator was used with an operator which does not does not support ancillary operators

Action: Remove the ancillary operator in the query

OCI-31053: The value of the depth argument in the operator cannot be negative

OCI-31053: The value of the depth argument in the operator cannot be negative

Cause: The value of the depth argument passed to the primary operator is not a positive integer

Action: Pass a positive value of the depth argument

OCI-31052: Cannot delete ACL with other references

OCI-31052: Cannot delete ACL with other references

Cause: The requested deletion of an ACL resource cannot proceed. The ACL is in use by other resources.

Action: Remove the resources that are making reference to the ACL in question and try again.

OCI-31051: Requested access privileges not supported

OCI-31051: Requested access privileges not supported

Cause: The requested access privileges are not supported for the specified resource.

Action: Ensure that the set of requested access privileges are valid access privileges for the specified resource.