Oracle 11g Error Codes and Solution Suggestions from ORA-19500 to ORA-19600
- ORA-19500: device block size string is invalid
- Cause: the device block size returned by sequential I/O OSD is invalid
- Action: If the block size was set by using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then the specified block size must be changed. If no PARMS option was specified on the ALLOCATE CHANNEL command, then this is an internal error that should be reported to Oracle.
- ORA-19501: read error on file “string“, block number string (block size=string)
- Cause: read error on input file
- Action: check the file
- ORA-19502: write error on file “string“, block number string (block size=string)
- Cause: write error on output file
- Action: check the file
- ORA-19503: cannot obtain information on device, name=”string“, type=”string“, parms=”string“
- Cause: call to get device information returned an error
- Action: check device name, type and parameters
- ORA-19504: failed to create file “string“
- Cause: call to create file returned an error
- Action: check additional messages, check access permissions
- ORA-19505: failed to identify file “string“
- Cause: call to identify the file returned an error
- Action: check additional messages, and check if the file exists
- ORA-19506: failed to create sequential file, name=”string“, parms=”string“
- Cause: call to create the sequential file returned an error
- Action: check additional messages, check access permissions
- ORA-19507: failed to retrieve sequential file, handle=”string“, parms=”string“
- Cause: call to retrieve the sequential file returned an error
- Action: check additional messages, and check if the file exists
- ORA-19508: failed to delete file “string“
- Cause: call to delete the file returned an error
- Action: check additional messages
- ORA-19509: failed to delete sequential file, handle=”string“, parms=”string“
- Cause: call to delete the sequential file returned an error
- Action: check additional messages
- ORA-19510: failed to set size of string blocks for file “string” (block size=string)
- Cause: call to resize the file returned an error
- Action: check additional messages
- ORA-19511: Error received from media manager layer, error text: string
- Cause: An error occurred in the media management software which is linked with the Oracle server to perform backup and restore in cooperation with Recovery Manager.
- Action: If the text of message 19511 does not provide enough information to resolve the problem, then you should contact the vendor of the media management software.
- ORA-19512: file search failed
- Cause: Recovery manager or Oracle Server attempted to discover files that matched the specified pattern but failed.
- Action: Check errors on the error stack for an explanation why the search for files could not be successfully executed.
- ORA-19513: failed to identify sequential file
- Cause: Unable to identify the sequential file.
- Action: Check additional messages, and check if the file exists on media.
- ORA-19525: tempfile for the clone database must be renamed
- Cause: Opening a clone database failed because Oracle server forces the tempfile to be renamed, in order to avoid overwriting the primary tempfile.
- Action: Rename the tempfiles manually or automatically by using the DB_FILE_NAME_CONVERT initialization parameter.
- ORA-19526: only one location allowed for parameter string
- Cause: A list of default locations was provided in an Oracle-managed files parameter.
- Action: Edit the parameter to include a single location.
- ORA-19527: physical standby redo log must be renamed
- Cause: An attempt was made to clear redo log at a physical standby database. Clearing an OMF redo log will not work unless DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter is specified. Clearing a non-OMF (or user-defined) redo log file will not work unless the LOG_FILE_NAME_CONVERT initialization parameter is set.
- Action: Set DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter for OMF redo log files and re-issue the operation that attempted to clear redo log. Set LOG_FILE_NAME_CONVERT parameter for non-OMF redo log files and re-issue the operation that attempted to clear redo log.
- ORA-19528: redo logs being cleared may need access to files
- Cause: The redo logs are being cleared. This procedure may need the files this operation is being applied to.
- Action: Wait for the redo logs to be cleared.
- ORA-19529: Pattern string in initialization parameter string has an Oracle Managed Files file name.
- Cause: An attempt was made to convert a database file name to an Oracle Managed Files file name using DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT initialization parameter. This was not a valid operation.
- Action: Retry the operation with a pattern template instead of a full Oracle Managed Files file name.
- ORA-19550: cannot use backup/restore functions while using dispatcher
- Cause: Attempted to use backup/restore functions while connected to the dispatcher in a shared server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process.
- Action: Connect directly to the instance then re-execute the backup or restore function.
- ORA-19551: device is busy, device type: string, device name: string
- Cause: The indicated device could not be allocated because it is allocated to another session, or no device was named, or all devices of the requested type are busy.
- Action: Either attempt to allocate another device or wait until the required device is no longer busy.
- ORA-19552: device type string is invalid
- Cause: The device type indicated is invalid.
- Action: Supply a correct device type and retry the allocation.
- ORA-19553: device name string is invalid
- Cause: The device name indicated is invalid.
- Action: Supply a correct device name and retry the allocation.
- ORA-19554: error allocating device, device type: string, device name: string
- Cause: The specified device could not be allocated.
- Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
- ORA-19555: invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
- Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range.
- Action: Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. If the archive log parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2.
- ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred
- Cause: The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred when it was required to be enabled. The destination was deferred automatically when an ALTER SYSTEM command for parameter LOG_ARCHIVE_DEST defined a destination which duplicated an existing LOG_ARCHIVE_DUPLEX_DEST parameter destination.
- Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST parameter.
- ORA-19557: device error, device type: string, device name: string
- Cause: An error occurred in the platform-specific device code
- Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
- ORA-19558: error de-allocating device
- Cause: The specified device could not be de-allocated.
- Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
- ORA-19559: error sending device command: string
- Cause: An error occurred while sending the indicated command to the session device.
- Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
- ORA-19560: string is not a valid device limit name
- Cause: An invalid name of device limit was specified in a call to DBMS_BACKUP_RESTORE.SETLIMIT.
- Action: Use one of the device limit names described in dbmsbkrs.sql
- ORA-19561: string requires a DISK channel
- Cause: The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found.
- Action: Deallocate the current device and allocate a DISK channel, then then retry the command.
- ORA-19562: file string is empty
- Cause: The indicated file, which is an archived log, control file, or datafile was found to be empty during a copy, backup, or scan] operation.
- Action: Ensure that the correct files are being specified for the copy or backup operation.
- ORA-19563: string header validation failed for file string
- Cause: When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, its header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file) belonging to the current database.
- Action: Ensure that the correct files are being specified for the copy or backup operation.
- ORA-19564: error occurred writing string bytes at block number string
- Cause: An error occurred while writing to a file.
- Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation.
- ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
- Cause: An attempt was made to specify duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled.
- Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, or do not specify duplexing to sequential devices.
- ORA-19566: exceeded limit of string corrupt blocks for file string
- Cause: The user specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup.
- Action: None. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupt.
- ORA-19567: cannot shrink file string because it is being backed up or copied
- Cause: An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied.
- Action: Retry the resize after the backup or copy is complete.
- ORA-19568: a device is already allocated to this session
- Cause: A device cannot be allocated to a session if another device is already allocated.
- Action: Deallocate the current device
- ORA-19569: no device is allocated to this session
- Cause: An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated.
- Action: Allocate a device then retry the operation.
- ORA-19570: file number string is outside valid range of 1 through string
- Cause: A file number used in a copy, backup, or restore operation is not valid for the current database.
- Action: Specify a valid file number.
- ORA-19571: string RECID string STAMP string not found in control file
- Cause: The input file specified for a copy or backup operation could not be opened because the record describing the file is not found in the control file.
- Action: Specify a correct RECID/STAMP and retry the copy or backup.
- ORA-19572: cannot process file string, file is being being resized
- Cause: The input file specified for a copy or backup operation could not be opened because the file is being resized.
- Action: Wait for the resize to complete then retry the copy or backup.
- ORA-19573: cannot obtain string enqueue for datafile string
- Cause: The file access enqueue could not be obtained for a file specified in a backup, copy or restore operation. If the enqueue type shown is ‘shared’, then the file is the input file for a backup or copy. If the type is ‘exclusive’, then the file is the output file for a datafile copy or restore which is attempting to overwrite the currently active version of that file – in this case, the file must be offline or the database must be closed. If the type is ‘read-only’, then you are attempting to back up or copy this file while the database is in NOARCHIVELOG mode.
- Action: Wait until the conflicting operation is complete, then retry the copy or backup. If the database is in NOARCHIVELOG mode, then all files being backed up must be closed cleanly.
- ORA-19574: output file name must be specified
- Cause: This type of copy or restore requires an output file name.
- Action: Specify an output file name and retry the copy.
- ORA-19575: expected string blocks in file string, found string
- Cause: During a backup, restore, copy, or scan operation, the indicated file did not contain as many blocks as were indicated in the file header.
- Action: The input copy or backup piece is probably corrupt. If another backup or copy exists of the file that is being restored, then the corrupt file can be deleted from the recovery catalog and the operation can be restarted.
- ORA-19576: datafile string not defined in control file
- Cause: The specified file number was not found in the control file.
- Action: Specify a correct file number and retry the operation.
- ORA-19577: file string is MISSING
- Cause: A COPYDATAFILECOPY, RESTOREDATAFILETO or PROXYRESTOREDATAFILE function specified a file number but no output file name, indicating that the output file name should be taken from the control file. However, the control file entry for this file indicates that it was created for a file that was present in the data dictionary but not named during the last CREATE CONTROLFILE statement, so the name in the control file cannot be used for restoration.
- Action: Either specify an output file name or issue a SQL RENAME command to enter a valid name for this file in the control file.
- ORA-19578: end of volume while duplexing to sequential files, backup piece incomplete
- Cause: An end of volume (EOV) condition was detected while duplexing to sequential files, and this condition cannot be handled currently.
- Action: Before retrying the backup, make sure the backup pieces will fit in the volume, or disable duplexing.
- ORA-19579: archived log record for string not found
- Cause: No archived log record corresponding to input file could be found in the control file.
- Action: Specify a valid archived log file name and retry the operation.
- ORA-19580: string conversation not active
- Cause: A backup or restore operation was attempted before a conversation was started.
- Action: Start a conversation then retry the operation.
- ORA-19581: no files have been named
- Cause: An attempt was made to proceed from the file naming phase to the piece processing phase of a backup or restore conversation before any files have been specified for backup or restore.
- Action: Specify some files then retry the operation.
- ORA-19582: archived log file header validation for string failed
- Cause: Archived log file header is corrupt and could not be validated.
- Action: Provide a valid archived log file and retry the operation.
- ORA-19583: conversation terminated due to error
- Cause: An error occurred which forced the termination of the current backup or restore conversation.
- Action: There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation.
- ORA-19584: file string already in use
- Cause: The indicated file, which was specified as the target for a copy, restore, or delete operation is already in use by the database.
- Action: Specify a different name and retry the operation.
- ORA-19585: premature end of volume on piece string
- Cause: While creating the indicated backup piece, an end-of-volume condition was encountered before all of the backup set control data was written to the backup piece. This is most likely a media error, because the amount of backup set control data is very small in relation to the total amount of data in a backup set.
- Action: Retry the piece with a larger piece of output media.
- ORA-19586: string k-byte limit is too small to hold piece directory
- Cause: The user-specified limit for MAXPIECESIZE for this channel is not enough to hold the backup set control data.
- Action: Allocate a channel specifying a larget valule for MAXPIECESIZE and retry the operation.
- ORA-19587: error occurred reading string bytes at block number string
- Cause: An error occurred while reading from a file.
- Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error then retry the copy, backup, or restore operation.
- ORA-19588: string RECID string STAMP string is no longer valid
- Cause: The indicated record has been marked as deleted. This indicates that the corresponding file has either been overwritten by another copy or restore, or that the copy was ‘consumed’ by a SWITCHTOCOPY operation.
- Action: If you know the name of the file you wish to copy, then inspect it and then retry the copy specifying the new RECID.
- ORA-19589: string is not a snapshot or backup control file
- Cause: The control file that is the source for a backup or copy operation is not a snapshot or backup control file.
- Action: Specify the name of a snapshot or backup control file.
- ORA-19590: conversation already active
- Cause: You tried to begin a backup or restore conversation, but another conversation is already active in this session.
- Action: Either continue the current conversation, or call BACKUPCANCEL or RESTORECANCEL to end the current conversation before starting a new one.
- ORA-19591: backup aborted because job time exceeded duration time
- Cause: You tried to backup with duration option and the time provided was not sufficient to complete the backup.
- Action: Adjust the duration time and re-run the command. Or run the backup command without duration option.
- ORA-19592: wrong string conversation type
- Cause: You attempted to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, you specified an archived log to be included in a datafile backup set. The specified file will not be included in the backup or restore operation.
- Action: No action required – the conversation is still active, and more files can be specified.
- ORA-19593: datafile number string already included as string
- Cause: This datafile is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of a datafile.
- Action: No action required – the conversation is still active, and more files can be specified.
- ORA-19594: control file already included as string
- Cause: The control file is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the control file.
- Action: No action required – the conversation is still active, and more files can be specified.
- ORA-19595: archived log string already included in backup conversation
- Cause: The indicated archived log has already been specified for inclusion in this backup conversation.
- Action: No action required – the conversation is still active, and more files can be specified.
- ORA-19596: SPFILE already included
- Cause: The SPFILE is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the SPFILE.
- Action: No action required – the conversation is still active, and more files can be specified.
- ORA-19597: file string block size string does not match set block size of string
- Cause: A file was specified for inclusion in a backup set but it has a logical block size different from the rest of the files in the backup set. All files in a backup set must have the same logical block size.
- Action: Specify a file that has the same block size as the rest of the files in the backup set. The conversation is still active and more files can be specified.
- ORA-19598: 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.
- ORA-19599: block number string is corrupt in string string
- Cause: A corrupt block was found in a control file, archived log, or backup piece that is being read for a backup or copy. Corruption shall not be tolerated in control files, archived logs, or backup pieces.
- Action: None. The copy or backup operation fails. Note that in the case of a backup set, the conversation is still active and the piece may be retried.
- ORA-19600: input file is string string (string)
- Cause: This message identifies the input file for a failed copy operation. Both the file number and name (if the name has been determined) are shown. For a datafile, the file number refers to the datafile’s absolute file number as shown in the DBA_DATA_FILES view. For a datafile copy, the file number refers to the copy’s control file record number as shown in the RECID column of the V$DATAFILE_COPY view. For an archived log, the file number refers to the log’s control file record number as shown in the RECID column of the V$ARCHIVED_LOG view.
- Action: See other error message.