back
Oracle® Database 11g / 12c / 18c error codes ORA-19500-ORA-19960
- ORA-19500: device block size [string] is invalid
- ORA-19501: read error on file "[string]", block number [string] (block size=[string])
- ORA-19502: write error on file "[string]", block number [string] (block size=[string])
- ORA-19503: cannot obtain information on device, name="[string]", type="[string]", parms="[string]"
- ORA-19504: failed to create file "[string]"
- ORA-19505: failed to identify file "[string]"
- ORA-19506: failed to create sequential file, name="[string]", parms="[string]"
- ORA-19507: failed to retrieve sequential file, handle="[string]", parms="[string]"
- ORA-19508: failed to delete file "[string]"
- ORA-19509: failed to delete sequential file, handle="[string]", parms="[string]"
- ORA-19510: failed to set size of [string] blocks for file "[string]" (block size=[string])
- ORA-19511: Error received from media manager layer, error text: [string]
- ORA-19512: file search failed
- ORA-19513: failed to identify sequential file
- ORA-19525: tempfile for the clone database must be renamed
- ORA-19526: only one location allowed for parameter [string]
- ORA-19527: physical standby redo log must be renamed
- ORA-19528: redo logs being cleared may need access to files
- ORA-19529: Pattern [string] in initialization parameter [string] has an Oracle Managed Files file name.
- ORA-19550: cannot use backup/restore functions while using dispatcher
- ORA-19551: device is busy, device type: [string], device name: [string]
- ORA-19552: device type [string] is invalid
- ORA-19553: device name [string] is invalid
- ORA-19554: error allocating device, device type: [string], device name: [string]
- ORA-19555: invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
- ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred
- ORA-19557: device error, device type: [string], device name: [string]
- ORA-19558: error de-allocating device
- ORA-19559: error sending device command: [string]
- ORA-19560: [string] is not a valid device limit
- ORA-19561: [string] requires a DISK channel
- ORA-19562: file [string] is empty
- ORA-19563: [string] header validation failed for file [string]
- ORA-19564: error occurred writing [string] bytes at block number [string]
- ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
- ORA-19566: exceeded limit of [string] corrupt blocks for file [string]
- ORA-19567: cannot shrink file [string] because it is being backed up or copied
- ORA-19568: a device is already allocated to this session
- ORA-19569: no device is allocated to this session
- ORA-19570: file number [string] is outside valid range of 1 through [string]
- ORA-19571: [string] RECID [string] STAMP [string] not found in control file
- ORA-19572: cannot process file [string], file is being being resized
- ORA-19573: cannot obtain [string] enqueue for datafile [string]
- ORA-19574: output file name must be specified
- ORA-19575: expected [string] blocks in file [string], found [string]
- ORA-19576: datafile [string] not defined in control file
- ORA-19577: file [string] is MISSING
- ORA-19578: end of volume while duplexing to sequential files, backup piece incomplete
- ORA-19579: archived log record for [string] not found
- ORA-19580: [string] conversation not active
- ORA-19581: no files have been named
- ORA-19582: archived log file header validation for [string] failed
- ORA-19583: conversation terminated due to error
- ORA-19584: file [string] already in use
- ORA-19585: premature end of volume on piece [string]
- ORA-19586: [string] k-byte limit is too small to hold piece directory
- ORA-19587: error occurred reading [string] bytes at block number [string]
- ORA-19588: [string] RECID [string] STAMP [string] is no longer valid
- ORA-19589: [string] is not a snapshot or backup control file
- ORA-19590: conversation already active
- ORA-19591: backup aborted because job time exceeded duration time
- ORA-19592: wrong [string] conversation type
- ORA-19593: datafile number [string] already included as [string]
- ORA-19594: control file already included as [string]
- ORA-19595: archived log [string] already included in backup conversation
- ORA-19596: SPFILE already included
- ORA-19597: file [string] block size [string] does not match set block size of [string]
- ORA-19598: can not backup SPFILE because the instance was not started with SPFILE
- ORA-19599: block number [string] is corrupt in [string] [string]
- ORA-19600: input file is [string] [string] ([string])
- ORA-19601: output file is [string] [string] ([string])
- ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
- ORA-19603: cannot backup or copy active file with KEEP .. UNRECOVERABLE option
- ORA-19604: conversation file naming phase is over
- ORA-19605: input file name must be specified
- ORA-19606: Cannot copy or restore to snapshot control file
- ORA-19607: [string] is an active control file
- ORA-19608: [string] is not a backup piece
- ORA-19609: [string] is from different backup set: stamp [string] count [string]
- ORA-19610: directory block [string] is corrupt
- ORA-19611: backup piece out of order. Expected [string] but found [string]
- ORA-19612: datafile [string] not restored due to [string]
- ORA-19613: datafile [string] not found in backup set
- ORA-19614: archived log thread [string] sequence [string] not found in backup set
- ORA-19615: some files not found in backup set
- ORA-19616: output file name must be specified if database not mounted
- ORA-19617: file [string] contains different RESETLOGS data
- ORA-19618: cannot name files after RESTOREVALIDATE has been called
- ORA-19619: cannot call RESTOREVALIDATE after files have been named
- ORA-19620: [string] is not of [string] type
- ORA-19621: archived log range has already been specified
- ORA-19622: archived log thread [string] sequence [string] not restored due to [string]
- ORA-19623: file [string] is open
- ORA-19624: operation failed, retry possible
- ORA-19625: error identifying file [string]
- ORA-19626: backup set type is [string] - can not be processed by this conversation
- ORA-19627: cannot read backup pieces during control file application
- ORA-19628: invalid SCN range
- ORA-19629: no files in specified archived log SCN range
- ORA-19630: end of volume encountered while copying backup piece
- ORA-19631: archived log record contains no file name
- ORA-19632: file name not found in control file
- ORA-19633: control file record [string] is out of sync with recovery catalog
- ORA-19634: file name required for this function
- ORA-19635: input and output file names are identical: [string]
- ORA-19636: archived log thread [string] sequence [string] already included
- ORA-19637: BACKUPPIECECREATE requires file name when using DISK device
- ORA-19638: file [string] is not current enough to apply this incremental backup
- ORA-19639: file [string] is more current than this incremental backup
- ORA-19640: datafile checkpoint is SCN [string] time [string]
- ORA-19641: backup datafile checkpoint is SCN [string] time [string]
- ORA-19642: start SCN of incremental backup is [string]
- ORA-19643: datafile [string]: incremental-start SCN is too recent
- ORA-19644: datafile [string]: incremental-start SCN is prior to RESETLOGS SCN [string]
- ORA-19645: datafile [string]: incremental-start SCN is prior to creation SCN [string]
- ORA-19646: cannot change size of datafile [string] from [string] to [string]
- ORA-19647: non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
- ORA-19648: datafile [string]: incremental-start SCN equals checkpoint SCN
- ORA-19649: offline-range record RECID [string] STAMP [string] not found in file [string]
- ORA-19650: Offline-range record RECID [string] STAMP [string] in file [string] has SCN [string]
- ORA-19651: cannot apply offline-range record to datafile [string]: SCN mismatch
- ORA-19652: cannot apply offline-range record to datafile [string]: file is fuzzy
- ORA-19653: cannot switch to older file incarnation
- ORA-19654: must use backup control file to switch file incarnations
- ORA-19655: cannot switch to incarnation with different RESETLOGS data
- ORA-19656: cannot backup, copy, or delete online log [string]
- ORA-19657: cannot inspect current datafile [string]
- ORA-19658: cannot inspect [string] - file is from different RESETLOGS
- ORA-19659: incremental restore would advance file [string] past RESETLOGS
- ORA-19660: some files in the backup set could not be verified
- ORA-19661: datafile [string] could not be verified
- ORA-19662: archived log thread [string] sequence [string] could not be verified
- ORA-19663: cannot apply current offline range to datafile [string]
- ORA-19664: file type: [string], file name: [string]
- ORA-19665: size [string] in file header does not match actual file size of [string]
- ORA-19666: cannot do incremental restore of the control file
- ORA-19667: cannot do incremental restore of datafile [string]
- ORA-19668: cannot do full restore of datafile [string]
- ORA-19669: proxy copy functions cannot be run on DISK channel
- ORA-19670: file [string] already being restored
- ORA-19671: media management software returned invalid proxy handle
- ORA-19672: media management software returned invalid file status
- ORA-19673: error during proxy copy of file [string]
- ORA-19674: file [string] is already being backed up with proxy copy
- ORA-19675: file [string] was modified during proxy copy
- ORA-19676: one or more files failed during proxy backup or restore
- ORA-19677: RMAN configuration name exceeds maximum length of [string]
- ORA-19678: RMAN configuration value exceeds maximum length of [string]
- ORA-19679: RMAN configuration number [string] is outside valid range of 1 through [string]
- ORA-19680: some blocks not recovered. See trace file for details
- ORA-19681: block media recovery on control file not possible
- ORA-19682: file [string] not in block media recovery context
- ORA-19683: real and backup block size of file [string] are unequal
- ORA-19684: block media recovery failed because database is suspended
- ORA-19685: SPFILE could not be verified
- ORA-19686: SPFILE not restored due to [string]
- ORA-19687: SPFILE not found in backup set
- ORA-19688: control file AUTOBACKUP format([string]) for [string] does not have %F
- ORA-19689: cannot have more than one %F in control file AUTOBACKUP format([string]) for [string]
- ORA-19690: backup piece release [string] incompatible with Oracle release [string]
- ORA-19691: [string] is from different database: id=[string], name=[string]
- ORA-19692: missing creation stamp on piece [string]
- ORA-19693: backup piece [string] already included
- ORA-19694: some changed blocks were not found in the change tracking file
- ORA-19695: fixed table X$KRBMSFT has not been populated
- ORA-19696: control file not found in backup set
- ORA-19697: standby control file not found in backup set
- ORA-19698: [string] is from different database: id=[string], db_name=[string]
- ORA-19699: cannot make copies with compression enabled
- ORA-19700: device type exceeds maximum length of [string]
- ORA-19701: device name exceeds maximum length of [string]
- ORA-19703: device command [string] exceeds maximum length of [string]
- ORA-19704: file name exceeds maximum length of [string]
- ORA-19705: tag value exceeds maximum length of [string] characters
- ORA-19706: invalid SCN
- ORA-19707: invalid record block number - [string]
- ORA-19708: log destination exceeds maximum length of [string] characters
- ORA-19709: numeric parameter must be non-negative integer
- ORA-19710: unsupported character set [string]
- ORA-19711: cannot use RENORMALIZEALLFILENAMES while database is open
- ORA-19712: table name exceeds maximum length of [string]
- ORA-19713: invalid copy number: [string]
- ORA-19714: length for generated name longer than [string]
- ORA-19715: invalid format [string] for generated name
- ORA-19716: error processing format [string] to generate name for backup
- ORA-19717: for non-OMF search the pattern must be specified
- ORA-19718: length for command id longer than [string]
- ORA-19719: length for operation name longer than [string]
- ORA-19720: Error occurred when converting an OCI number into an SCN
- ORA-19721: Cannot find datafile with absolute file number [string] in tablespace [string]
- ORA-19722: datafile [string] is an incorrect version
- ORA-19723: Cannot recreate plugged in read-only datafile [string]
- ORA-19724: snapshot too old: snapshot time is before file [string] plug-in time
- ORA-19725: can not acquire plug-in enqueue
- ORA-19726: cannot plug data [string] at level string into database running at compatibility level string
- ORA-19727: cannot plug data [string] at level string into database running Oracle string
- ORA-19728: data object number conflict between table [string] and partition [string] in table [string]
- ORA-19729: File [string] is not the initial version of the plugged in datafile
- ORA-19730: can not convert offline plugged-in datafile [string]
- ORA-19731: cannot apply change to unverified plugged-in datafile [string]
- ORA-19732: incorrect number of datafiles for tablespace [string]
- ORA-19733: COMPATIBLE parameter needs to be [string] or greater
- ORA-19734: wrong creation SCN - control file expects converted plugged-in datafile
- ORA-19735: wrong creation SCN - control file expects initial plugged-in datafile
- ORA-19736: can not plug a tablespace into a database using a different national character set
- ORA-19738: cannot find language information for character set: '[string]'
- ORA-19740: text is longer than [string]
- ORA-19750: change tracking file: '[string]'
- ORA-19751: could not create the change tracking file
- ORA-19752: block change tracking is already enabled
- ORA-19753: error writing to change tracking file
- ORA-19754: error reading from change tracking file
- ORA-19755: could not open change tracking file
- ORA-19756: corrupt block number [string] found in change tracking file
- ORA-19757: could not resize change tracking file to [string] blocks
- ORA-19758: failed to enable/disable block change tracking: out of SGA memory
- ORA-19759: block change tracking is not enabled
- ORA-19760: error starting change tracking
- ORA-19761: block size [string] is not valid for change tracking file
- ORA-19762: invalid file type [string]
- ORA-19763: compatibility version [string] is higher than maximum allowed: [string]
- ORA-19764: database id [string] does not match database id [string] in control file
- ORA-19765: mount id [string] does not match mount id [string] in control file
- ORA-19766: missing CHANGE keyword
- ORA-19767: missing TRACKING keyword
- ORA-19768: USING clause only valid with ENABLE CHANGE TRACKING
- ORA-19769: missing FILE keyword
- ORA-19770: invalid change tracking file name
- ORA-19771: cannot rename change tracking file while database is open
- ORA-19772: change tracking file name exceeds limit of [string] characters
- ORA-19773: must specify change tracking file name
- ORA-19776: PROXY restore to ASM disk group "[string]" is not supported.
- ORA-19777: ASM file [string] cannot be proxy backed up.
- ORA-19779: could not obtain resilvering status for change tracking file
- ORA-19800: Unable to initialize Oracle Managed Destination
- ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set
- ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
- ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - [string])
- ORA-19804: cannot reclaim [string] bytes disk space from [string] limit
- ORA-19805: RECID [string] of [string] was deleted to reclaim disk space
- ORA-19806: cannot make duplex backups in recovery area
- ORA-19808: recovery destination parameter mismatch
- ORA-19809: limit exceeded for recovery files
- ORA-19810: Cannot create temporary control file [string] in DB_RECOVERY_FILE_DEST
- ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
- ORA-19812: cannot use [string] without DB_RECOVERY_FILE_DEST
- ORA-19813: cannot have unavailable file [string] in DB_RECOVERY_FILE_DEST
- ORA-19815: WARNING: [string] of [string] bytes is [string]% used, and has [string] remaining bytes available.
- ORA-19816: WARNING: Files may exist in [string] that are not known to database.
- ORA-19830: error from target database: [string]
- ORA-19831: incompatible [string].[string].[string].[string] DBMS_BACKUP_RESTORE package: [string].[string].[string].[string] required
- ORA-19851: OS error while managing auxiliary database [string]
- ORA-19852: error creating services for auxiliary instance [string] (error [string])
- ORA-19853: error preparing auxiliary instance [string] (error [string])
- ORA-19854: error obtaining connect [string] from target
- ORA-19860: piece validation cannot be performed more than once
- ORA-19861: additional backup pieces cannot be validated in this conversation
- ORA-19862: backup pieces must be validated before accessing results
- ORA-19863: device block size [string] is larger than max allowed: [string]
- ORA-19865: Backup piece [string] has no data
- ORA-19866: error writing file header for datafile [string]
- ORA-19870: error while restoring backup piece [string]
- ORA-19873: cannot apply this backup section to file [string]
- ORA-19874: cannot finish multi-section restore to file [string]
- ORA-19875: multi-section restore not complete for file [string]
- ORA-19880: Corrupted space header for datafile [string], block [string]
- ORA-19881: Corrupted space bitmap for datafile [string], block [string]
- ORA-19882: datafile [string] checkpoint [string] is ahead of space bitmap datafile [string] checkpoint [string]
- ORA-19883: Unused Block Optimization stopped for datafile [string]
- ORA-19900: RESETLOGS must be specified after recovery to new incarnation
- ORA-19901: database needs more recovery to create new incarnation
- ORA-19902: incarnation key [string] not found
- ORA-19903: test recovery not allowed when recovering to new incarnation
- ORA-19904: test recovery not allowed for datafile [string]
- ORA-19905: log_archive_format must contain %s, %t and %r
- ORA-19906: recovery target incarnation changed during recovery
- ORA-19907: recovery time or SCN does not belong to recovered incarnation
- ORA-19908: datafile [string] has invalid checkpoint
- ORA-19909: datafile [string] belongs to an orphan incarnation
- ORA-19910: can not change recovery target incarnation in control file
- ORA-19911: datafile [string] contains future changes at the incarnation boundary
- ORA-19912: cannot recover to target incarnation [string]
- ORA-19913: unable to decrypt backup
- ORA-19914: unable to encrypt backup
- ORA-19915: unable to encrypt pre-10.2 files
- ORA-19916: [string]
- ORA-19919: encrypted backups to tertiary storage require Oracle Secure Backup
- ORA-19921: maximum number of [string] rows exceeded
- ORA-19922: there is no parent row with id [string] and level [string]
- ORA-19923: the session for row with id [string] is not active
- ORA-19924: there are no row with id [string]
- ORA-19926: Database cannot be converted at this time
- ORA-19927: CONVERT DATABASE operation cannot proceed
- ORA-19930: file [string] has invalid checkpoint SCN [string]
- ORA-19931: file [string] has invalid creation SCN [string]
- ORA-19932: control file is not clone or standby
- ORA-19941: invalid blocksize in cross platform datafile [string]
- ORA-19942: datafile copy [string] not created with compatibility 10.0 or greater
- ORA-19943: The current database incarnation changed during backup
- ORA-19951: cannot modify control file until DBNEWID is completed
- ORA-19952: database should be mounted exclusively
- ORA-19953: database should not be open
- ORA-19954: control file is not current
- ORA-19955: only one open thread is allowed to change the DBID
- ORA-19956: database should have no offline immediate datafiles
- ORA-19957: database should have no datafiles in unknown state
- ORA-19958: potential deadlock involving DIAG process
- ORA-19960: Internal use only