ORA-01201: file string header failed to write correctly
Cause: An I/O error was reported for the file header. The error was trapped and a second attempt will be made.
Action: The file probably will require recovery. Further error messages will indicate what is needed.
ORA-01202: wrong incarnation of this file - wrong creation time
Cause: The creation time in the file header is not the same as the creation time in the control file. This is probably a copy of a file that was dropped.
Action: Restore a current copy of the data file and do recovery as needed.
ORA-01203: wrong incarnation of this file - wrong creation SCN
Cause: The creation SCN in the file header is not the same as the creation SCN in the control file. This is probably a copy of a file that was dropped.
Action: Restore a current copy of the data file and do recovery as needed.
ORA-01204: file number is string rather than string - wrong file
Cause: The file number in the file header is not correct. This is probably a restored backup of the wrong file, but from the same database.
Action: Restore a copy of the correct data file and do recovery as needed.
ORA-01205: not a data file - type number in header is string
Cause: The file type in the header is not correct for a data file. This is probably a log file or control file. If the type is not a small non-zero positive number then the header is corrupted.
Action: Restore a copy of the correct data file and do recovery as needed.
ORA-01206: file is not part of this database - wrong database id
Cause: The database ID in the file header does not match the database id in the control file. The file may be from a different database, or it may not be a database file at all. If the database was rebuilt, this may be a file from before the rebuild. Note that if you see this error when the file is supposed to be plugged in from another database via the Transportable Tablespace feature, it means the database ID in the file header does not match the one expected.
Action: Restore a copy of the correct data file and do recovery as needed.
ORA-01207: file is more recent than control file - old control file
Cause: The control file change sequence number in the data file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.
Action: Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery.
ORA-01208: data file is an old version - not accessing current version
Cause: The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use.
Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.
ORA-01209: data file is from before the last RESETLOGS
Cause: The reset log data in the file header does not match the control file. If the database is closed or the file is offline, the backup is old because it was taken before the last ALTER DATABASE OPEN RESETLOGS command. If opening a database that is open already by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use.
Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.
ORA-01210: data file header is media corrupt
Cause: The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistancy of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database.
Action: Have operating system make correct file available to database. If the trace file dump indicates that only the checksum is wrong, restore from a backup and do media recovery.
ORA-01211: Oracle7 data file is not from migration to Oracle8
Cause: The file is not a copy of the file LAST used under Oracle7. This datafile is either a backup taken from before the migration, or the database was opened by Oracle7 after the migration utility was run. When converting a database from Oracle7 to Oracle8, the migration program MUST be the LAST utility to access the database under Oracle7. Only the datafiles that were current when the migration was done may be accessed by Oracle8.
Action: Have operating system make correct data file available to database, or repeat the Oracle7 to Oracle8 migration. Make sure that database is NOT opened after migration utility is run.
ORA-01212: MAXLOGMEMBERS may not exceed string
Cause: MAXLOGMEMBERS specified on the command line too large.
Action: Resubmit the command with a smaller MAXLOGMEMBERS
ORA-01213: MAXINSTANCES may not exceed string
Cause: MAXINSTANCES specified on the command line too large.
Action: Resubmit the command with a smaller MAXINSTANCES
ORA-01214: MAXLOGHISTORY may not exceed string
Cause: MAXLOGHISTORY specified on the command line too large.
Action: Resubmit the command with a smaller MAXLOGHISTORY
ORA-01215: enabled thread string is missing after CREATE CONTROLFILE
Cause: A CREATE CONTROLFILE statement was given which did not list all the enabled threads for the database.
Action: Reissue the CREATE CONTROLFILE statement, including all enabled threads.
ORA-01216: thread string is expected to be disabled after CREATE CONTROLFILE
Cause: A thread that was given during CREATE CONTROLFILE is enabled, but the datafiles indicate that it should be disabled. This is probably because the logs supplied to the CREATE CONTROLFILE are old (from before the disabling of the thread).
Action: This thread is not required to run the database. The CREATE CONTROLFILE statement can be reissued without the problem thread, and, if desired, the thread can be recreated after the database is open.
ORA-01217: logfile member belongs to a different logfile group
Cause: A member of a multiple-member logfile group specified in a CREATE CONTROLFILE is not part of the same group as previous members.
Action: Group together the correct members for the CREATE CONTROLFILE command.
ORA-01218: logfile member is not from the same point-in-time
Cause: A member of a multiple-member logfile group is from a different point in time. One of the members specified may be an older (backup) copy of the log.
Action: Find the correct version of the log, or leave it out of the CREATE CONTROLFILE command.
ORA-01219: database not open: queries allowed on fixed tables/views only
Cause: A query was issued against an object not recognized as a fixed table or fixed view before the database has been opened.
Action: Re-phrase the query to include only fixed objects, or open the database.
ORA-01220: file based sort illegal before database is open
Cause: A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open.
Action: Re-phrase the query to avoid a large sort, increase the values of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE initialization parameters to enable the sort to be done in memory.
ORA-01221: data file string is not the same file to a background process
Cause: When the database writer opens the data file, it is accessing a different physical file than the foreground doing the recovery. The timestamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all.
Action: Look in the DBWR trace file for the error it recieved when attempting to read the file header. Reconfigure the operating system as needed to have the file name successfully access the same file when opened by a background process.
ORA-01222: MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
Cause: Attemping to create a database or control file that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.
Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.
ORA-01223: RESETLOGS must be specified to set a new database name
Cause: The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS.
Action: Either add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE.
ORA-01224: group number in header string does not match GROUP string
Cause: Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong.
Action: Omit the GROUP option or give the correct one.
ORA-01225: thread number string is greater than MAXINSTANCES string
Cause: The log is for a thread greater than the MAXINSTANCES argument.
Action: Increase the value for MAXINSTANCES and resubmit the command.
ORA-01226: file header of log member is inconsistent with other members
Cause: The log file member in the accompanying error is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted log.
Action: Find the correct log member or omit this member from the command.
ORA-01227: log string is inconsistent with other logs
Cause: The log file in the accompanying error is inconsistent with the contents of other logs given in the CREATE CONTROLFILE command. Either a file header is corrupted, or some file is an old copy rather than the current version. The problem may not be with the log listed since all that can be detected is that there is an inconsistancy. All log files listed in the command must be the current versions of the online logs.
Action: Find the correct online logs or use the RESETLOGS option.
ORA-01228: SET DATABASE option required to install seed database
Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database id. Both the SET DATABASE and RESETLOGS options must be specified to create the control file for this database.
Action: Resubmit command with the SET DATABASE and RESETLOGS options.
ORA-01229: data file string is inconsistent with logs
Cause: The data file in the accompanying error is inconsistent with the contents of the logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online logs was missing from the command. It is also possible that one or more of the logs is an old copy rather than the current version. All online log files must be listed in the command and must be the current versions of the online logs.
Action: Find the correct online logs or use the RESETLOGS option.
ORA-01230: cannot make read only - file string is offline
Cause: An attempt to make a tablespace read only found that one of its files is offline.
Action: Bring the file online and retry this command.
ORA-01231: cannot make read write - file string is offline
Cause: An attempt to make a tablespace read write found that one of its files is offline.
Action: Bring the file online and retry this command.
ORA-01232: cannot start online backup - file string is being made read-only
Cause: An attempt to start an online backup found that one of the files is in transition to read-only mode.
Action: Wait for the transition to complete and then retry the command, if this is an ALTER DATABASE BEGIN BACKUP command, or take the backup without any begin or end commands, if this is an ALTER TABLESPACE BEGIN BACKUP command.
ORA-01233: file string is read only - cannot recover using backup control file
Cause: An attempt to do media recovery using a backup control file found that one of the files is marked read only. Read only files do not normally need to be recovered, but recovery with a backup control file must recover all online files.
Action: If the file really is read only, take it offline before the recovery, and bring the read only tablespace online after the database is open. If the file does need recovery use a control file from the time the file was read-write. If the correct control file is not available, use CREATE CONTROLFILE to make one.
ORA-01234: cannot end backup of file string - file is in use or recovery
Cause: Attempted to end an online backup of file when the file is busy. Some operation such as recovery or rename may be active, or there may still be some instance that has the database open with this file online.
Action: If there is an instance with the database open then the backup can be ended there by using the ALTER TABLESPACE command. Otherwise wait for the completion of the other operation.
ORA-01235: END BACKUP failed for string file(s) and succeeded for string
Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded.
Action: See the accompanying error messages for the reason the backups could not be ended. Any files not listed in the error messages were successful.
ORA-01236: Error string occurred during initialization of file header access
Cause: The indicated error occurred while doing initialization processing of file headers.
Action: The error indicated should be corrected. An attempt is made to recover from this error by using a slower access algorithm.
ORA-01237: cannot extend datafile string
Cause: An operating system error occurred during the resize.
Action: Fix the cause of the operating system error and retry the command.
ORA-01238: cannot shrink datafile string
Cause: An operating system error occurred during the resize.
Action: The error is ignored, operation continues normally.
ORA-01239: database must be in ARCHIVELOG mode to use external cache
Cause: An online file uses an external cache, but the database is in NOARCHIVELOG mode. Since an external cache may require media recovery this can not be allowed.
Action: Change database to be in ARCHIVELOG mode or do not use an external cache.
ORA-01240: too many data files to add in one command
Cause: The command specifies adding more data files than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large.
Action: If this is a CREATE TABLESPACE command, create with fewer files then add the other files later. If this is an ADD DATAFILE command, break it up into multiple commands.
ORA-01241: an external cache has died
Cause: The external cache may have been restarted.
Action: Take the file mentioned in the error stack offline, perform media recovery, bring the file online, and retry the attempted operation. You may also restart all instances to make sure they access all data files through consistent external caches.
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Cause: The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure.
Action: Restore accessibility to the file mentioned in the error stack and restart the instance.
ORA-01243: system tablespace file suffered media failure
Cause: A system tablespace file was detected as inaccessible due to media failure.
Action: Restore accessibility to the file mentioned in the error stack and restart the instance.
ORA-01244: unnamed datafile(s) added to control file by media recovery
Cause: Media recovery with a backup control file or a control file that was rebuilt, encountered the creation of a datafile that was not in the control file. An entry has been added to the control file for the new datafiles, but with the file name UNNAMEDnnnn, where nnnn is the file number. Attached errors describe the file names that were originally used to create the files.
Action: Rename the files to valid file names and resume recovery. If necessary the command ALTER DATABASE CREATE DATAFILE may be used to create a file suitable for recovery and do the rename. If the file is not going to be recovered then take it offline with the FOR DROP option.
ORA-01245: offline file string will be lost if RESETLOGS is done
Cause: Attempting to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the FOR DROP option.
Action: Either bring the file online and recover it, or take it offline with the FOR DROP option.
ORA-01246: recovering files through TSPITR of tablespace string
Cause: The files named in the accompanying errors are backups that were made before a tablespace point in time recovery of this tablespace. They cannot be recovered to a time after the point in time recovery.
Action: Restore more recent backups and recover them.
ORA-01247: database recovery through TSPITR of tablespace string
Cause: Recovery of the whole database encountered redo indicating there was a point in time recovery of the tablespace. The new version of the files in the tablespace should be included in the recovery, but that was not done.
Action: If the tablespace should not be recovered, take its file offline for drop. If it should be recovered, then restore or rename as needed and restart the recovery.
ORA-01248: file string was created in the future of incomplete recovery
Cause: Attempting to do a RESETLOGS open with a file entry in the control file that was originally created after the UNTIL time of the incomplete recovery. Allowing such an entry may hide the version of the file that is needed at this time. The file number may be in use for a different file which would be lost if the RESETLOGS was allowed.
Action: If more recovery is desired then apply redo until the creation time of the file is reached. If the file is not wanted and the same file number is not in use at the stop time of the recovery, then the file can be taken offline with the FOR DROP option. Otherwise a different control file is needed to allow the RESETLOGS. Another backup can be restored and recovered, or a control file can be created via CREATE CONTROLFILE.
ORA-01249: archiving not allowed in a clone database
Cause: Attempting to archive an online redo log or enable archiving for a clone database.
Action: Do not attempt to archive from a clone. The archive log destination could easily be the same as the primary database destroying its archived logs. If archiving is needed then recreate database as not a clone.
ORA-01250: Error string occurred during termination of file header access
Cause: The indicated error occurred while terminating the processing of file headers. The error was other than a write error.
Action: The indicated error should be corrected.
ORA-01251: Unknown File Header Version read for file number string
Cause: Read of the file header returned a record but its version cannot be identified. Either the header has been corrupted, or the file is not a valid database file.
Action: Have the operating system make the correct file available to the database, or recover the file.
ORA-01252: cannot prevent writes - file string in recovery manager backup
Cause: An attempt to make a tablespace read only or offline normal found that a recovery manager proxy backup is in progress. If the file is made offline or read-only, then the file header cannot be updated when the backup is complete.
Action: Wait for the Recovery Manager backup to complete and retry this command.
ORA-01253: cannot start online backup - file string in recovery manager backup
Cause: The specified file is being backed up by Recovery Manager.
Action: Wait for the Recovery Manager proxy backup to complete before starting another backup.
ORA-01254: cannot end online backup - file string in recovery manager backup
Cause: The specified file is being backed up by Recovery Manager.
Action: Wait for the Recovery Manager proxy backup to complete. Recovery Manager backup mode cannot be initiated or terminated manually.
ORA-01255: cannot shutdown - file string in recovery manager backup
Cause: An attempt to shutdown normally found that a Recovery Manager backup is still in progress.
Action: Wait for the Recovery Manager proxy backup to complete and retry this command.
ORA-01256: error in locking database file string
Cause: The file is in use by another database instance.
Action: Determine which database instance legitimately owns the file.
ORA-01257: cannot reuse database file string, unknown file size
Cause: The size of the raw partion cannot be determined
Action: Add the datafile/logfile by specifying the size parameter.
ORA-01258: unable to delete temporary file string
Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES or ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES operation was not able to delete a temporary file in the database.
Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file.
ORA-01259: unable to delete datafile string
Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation was not able to delete a datafile in the tablespace.
Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file.
ORA-01260: warning: END BACKUP succeeded but some files found not to be in backup mode
Cause: END BACKUP completed successfully for all files that were in online backup mode. However one or more modifiable files were found not to be in online backup mode. Backup of those files (if it was done) can be invalid and, if restored, can result in an inconsistent database.
Action: Check the alert log for a list of the files that were found not to be in backup mode. If there is a possibility that those files have been modified during online backup, then replace their backups with new ones.
ORA-01261: Parameter string destination string cannot be translated
Cause: The value for the specified parameter contained a destination string that could not be translated.
Action: Use a valid destination string in the specified parameter.
ORA-01262: Stat failed on a file destination directory
Cause: Unable to get information about an Oracle managed files destination directory.
Action: Check the permissions on the directory or use a different directory name.
ORA-01263: Name given for file destination directory is invalid
Cause: The name given for an Oracle managed files destination does not correspond to a directory.
Action: Use a different name.
ORA-01264: Unable to create string file name
Cause: Unable to create an Oracle managed file name.
Action: , if possible, and retry the command.
ORA-01265: Unable to delete string string
Cause: An error prevented the file from being deleted.
Action: See the subsequent error messsages that describe the operating system error that prevented the file from being deleted. If possible, fix the problem and manually delete the file.
ORA-01266: Unable to create unique file name
Cause: Unable to create a unique file name for an Oracle managed file. Oracle tried several names but each file name was already in use in the default destination directory for the file type.
Action: Retry the operation. If that fails, also, it may be necessary to change the default destination directory for the file type and then retry.
ORA-01267: Failure getting date/time
Cause: Could not get date/time when trying to create unique file name.
Action: Internal error - contact Oracle Customer Support.
ORA-01268: invalid TEMPFILE clause for alter of permanent TABLESPACE
Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for a permanent tablespace.
Action: Retry with a DATAFILE clause.
ORA-01269: Destination parameter string is too long
Cause: The value for DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter was too long.
Action: Replace the destination value for the specified parameter with a shorter character string.
ORA-01270: string operation is not allowed if STANDBY_PRESERVES_NAMES is true
Cause: An operation that renames or adds/drops a file was attempted at a standby database and STANDBY_PRESERVES_NAMES is true.
Action: Set STANDBY_PRESERVES_NAMES false if the operation must be performed.
ORA-01271: Unable to create new file name for file string
Cause: During standby database recovery an error occurred when trying to create a new file name for the indicated file.
Action: Use the ALTER DATABASE CREATE DATAFILE command with a new unique name and then resume the standby database recovery.
ORA-01272: REUSE only allowed when a file name is provided.
Cause: The REUSE parameter was specified in a command without a file name.
Action: Either supply a file name or remove the REUSE parameter.
ORA-01273: STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher
Cause: Automated standby file management was disabled, so an added file
Action: Restart the instance with COMPATIBLE set to the correct release.
ORA-01274: cannot add datafile 'string' - file could not be created
Cause: Automated standby file management was disabled, so an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The control file file entry for the file is 'UNNAMEDnnnnn'.
Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery.
ORA-01275: Operation string is not allowed if standby file management is automatic.
Cause: An operation that renames, adds, or drops a file was attempted at a standby database and STANDBY_FILE_MANAGEMENT was set to AUTO.
Action: Set STANDBY_FILE_MANAGEMENT to MANUAL if the operation must be performed.
ORA-01276: Cannot add file string. File has an Oracle Managed Files file name.
Cause: An attempt was made to add to the database a datafile, log file, control file, snapshot control file, backup control file, datafile copy, control file copy or backuppiece with an Oracle Managed Files file name.
Action: Retry the operation with a new file name.
ORA-01277: file 'string' already exists
Cause: An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename' command specified a file name which is already in use.
Action: Either specify a different file name, or add the REUSE parameter to the command to overwrite the existing file.
ORA-01278: error creating file 'string'
Cause: An operating system error occurred while attempting to create a trace file specified in the command ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename'.
Action: Check the error stack for more detailed information.
ORA-01279: db_files too large
Cause: db_files has been set too high to be supported by the system.
Action: Decrease the number of db_files.
ORA-01280: Fatal LogMiner Error.
Cause: An internal error has occurred inside LogMiner.
Action: None
ORA-01281: SCN range specified is invalid
Cause: StartSCN may be greater than EndSCN, or the SCN specified may be invalid.
Action: Specify a valid SCN range.
ORA-01282: date range specified is invalid
Cause: startTime may be greater than endTime. startTime or endTime may be greater than year 2110. startTime may be less than year 1988.
Action: Specify a valid date range.
ORA-01283: Options specified is invalid
Cause: The specified options parameter is invalid for the procedure.
Action: Specify valid Options parameter.
ORA-01284: file string cannot be opened
Cause: The file or directory may not exist or may be inaccessible. Pathname exceeds 256 characters.
Action: Ensure that the file and the directory exist and are accessible.
ORA-01285: error reading file string
Cause: The file or directory may not exist or is inaccessible.
Action: Specify valid file or directory. Make sure that file and directory are accessible.
ORA-01286: start interval required
Cause: Options were supplied which require a starting time or starting SCN
Action: Specify a starting interval (time or SCN).
ORA-01287: file string is from a different database incarnation
Cause: The logfile is produced by a different incarnation of the database.
Action: Add a logfile that is produced by the same incarnation.
ORA-01288: cannot apply this DDL to the Logminer Dictionary
Cause: A command that is not supported by Logminer was present in a logfile. Commands that change the character set of the database are not supported by Logminer. "ALTER DATABASE SET TIME_ZONE" is not supported by Logminer.
Action: Do not execute unsupported commands when using Streams, Logical Standby, or Logminer. Turn off DDL tracking in order for Logminer to skip unsupported commands.
ORA-01289: cannot add duplicate logfile string
Cause: The logfile specified has already been added to the list of logfiles.
Action: Specify a different logfile.
ORA-01290: cannot remove unlisted logfile string
Cause: The user attempted to remove a logfile that is not present in the list.
Action: Specify a valid logfile.
ORA-01291: missing logfile
Cause: Not all logfiles corresponding to the time or scn range specified have been added to the list.
Action: Check the v$logmnr_logs view to determine the missing scn range, and add the relevant logfiles.
ORA-01292: no log file has been specified for the current LogMiner session
Cause: No logfile has been specified for the LogMiner session.
Action: Specify atleast one log file.
ORA-01293: mounted database required for specified LogMiner options
Cause: Options were specified which required the database to be mounted
Action: Specify different options or mount the database.
ORA-01294: error occurred while processing information in dictionary file string, possible corruption
Cause: The dictionary file is corrupt.
Action: Get a new dictionary file.
ORA-01295: DB_ID mismatch between dictionary string and logfiles
Cause: The dictionary file is produced by a database that is different from that produced the logfiles.
Action: Specify a compatible dictionary file.
ORA-01296: character set mismatch between dictionary string and logfiles
Cause: The character set of the database that produced the dictionary file is different from the charatcter set of the database that produced the logfiles.
Action: Specify a dictionary file with the same character set.
ORA-01297: redo version mismatch between dictionary string and logfiles
Cause: The redo version of the database generating the dictionary is different from the one generating the logfiles.
Action: None
ORA-01298: conflicting dictionary option
Cause: More than one dictionary source was specified or DDL_DICT_TRACKING was specified with DICT_FROM_ONLINE_CATALOG.
Action: None
ORA-01299: dictionary string corresponds to a different database incarnation
Cause: The dictionary file was extracted from a different incarnation of the database.
Action: Specify a dictionary file extracted from the correct database incarnation.
ORA-01300: writable database required for specified LogMiner options
Cause: Options were specified which required the database to be writable.
Action: Specify different options or open the database for write access.
ORA-01301: error writing to file during flat file build
Cause: Error writing to file during flat file build
Action: None
ORA-01302: dictionary build options missing or incorrect
Cause: Missing dictionary build options or incorrectly specified options
Action: Specify either a build to redo log or to flat file. If build to flat file, specify filename and directory.
ORA-01303: subordinate process error: number. Check alert and trace logs
Cause: A process subordinate to this Logminer process has exited with this error status.
Action: Search for this error in the alert log and trace files for additional information.
ORA-01304: subordinate process error. Check alert and trace logs
Cause: A process subordinate to this Logminer process has exited with an error condition.
Action: Look in the alert log and trace files for additional information.
ORA-01306: dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure.
Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view.
ORA-01307: no LogMiner session is currently active
Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure. Otherwise, dbms_logmnr.end_logmnr() was called without a prior call to dbms_logmnr.start_logmnr() or dbms_logmnr.add_logfile()
Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view.
ORA-01308: initialization parameter utl_file_dir is not set
Cause: utl_file_dir is not set in the initialization file.
Action: Set utl_file_dir to the appropriate directory.
ORA-01309: invalid session
Cause: The specified Logminer session ID or session handle is invalid.
Action: Use a valid Logminer session ID or session handle.
ORA-01310: requested return type not supported by the lcr_mine function
Cause: The return type requested by the user is not supported by lcr_mine"
Action: Pick a return type supported by the lcr_mine function"
ORA-01311: Illegal invocation of the mine_value function
Cause: An attempt was made to use mine_value function on a column other than redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS or SYS.V$LOGMNR_CONTENTS fixed table/view.
Action: Rewrite the SQL statement with a legal invocation of mine_value
ORA-01312: Specified table/column does not exist
Cause: The table/column specified in the lcr_mine call does not exist at the the specified SCN. The table/column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table/column correctly.
Action: Create a LogMiner session at a start SCN at which the table definition is available.
ORA-01313: LogMiner dictionary column type different from specified type
Cause: The return type specified for the column in lcr_mine call is different from the actual type of the column.
Action: Rewrite the lcr_mine invocation with the right return type.
ORA-01314: Name of the column to be mined should be a string literal
Cause: The fully qualified name of the column to be mined by the LogMiner functions should be string literal.
Action: If the fully qualified name of the column to be mined is a.b.c.d, enclose the column name in quotes as in 'a.b.c.d'.
ORA-01315: Log file has been added or removed during select
Cause: A redo log file has been added or removed while selecting on the v$logmnr_logs fixed view.
Action: Re-issue the SQL select statement on the v$logmnr_logs view.
ORA-01316: Already attached to a Logminer session
Cause: A Logminer attach session was issued while already attached to a Logminer session.
Action: Detach from the current Logminer session and attach to the requested session.
ORA-01317: Not attached to a Logminer session
Cause: A command or procedure was issued which requires an attached Logminer session.
Action: Attach to a Logminer session before issuing the command or procedure.
ORA-01319: Invalid Logminer session attribute
Cause: A session attribute was supplied which is invalid.
Action: Re-issue with valid session attribute.
ORA-01320: Invalid Logminer dictionar attribute
Cause: A Logminer dictionary attribute was supplied which is invalid.
Action: Re-issue with valid dictionary attribute.
ORA-01321: No Logminer Dictionary for requested start SCN
Cause: The requested session start SCN is less than the SCN of any available Logminer Dictionary build. It is not possible to unwind a Logminer Dictionary to the requested start SCN.
Action: Re-issue the start_logminer request with a start SCN for which a Logminer Dictionary is available.
ORA-01322: No such table
Cause: An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table().
Action: Re-issue with valid table name.
ORA-01323: Invalid state
Cause: A Logminer routine was called from the wrong state.
Action: None
ORA-01324: cannot add file string due to DB_ID mismatch
Cause: The logfile is produced by a different database than other logfiles already added to the list.
Action: Specify a logfile produced by the same database.
ORA-01325: archive log mode must be enabled to build into the logstream
Cause: Database does not have archivelog mode enabled.
Action: Mount the database, then issue commands to enable archivelog mode. startup pfile=init.ora mount alter database archivelog alter database open
ORA-01326: compatability of 9.0 or greater required to build into the logstream
Cause: Compatibility mode set to some value less than 9.0
Action: Ensure that init.ora parameter establishing a compatability of 9.0 or greater is set. For example: compatible=9.0.0.0.0
ORA-01327: failed to exclusively lock system dictionary as required by build
Cause: Other users are performing DDL operations.
Action: None
ORA-01328: only one build operation may occur at one time
Cause: Another processes is simultaneously attempting to run build();
Action: Wait until the other processes completes.
No hay comentarios:
Publicar un comentario