Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Managed Services. Talent Sourcing. Business Solutions Consulting Training. Resource Center. Privacy Policy Terms of Use. Action: Detach from the current Logminer session and attach to the requested 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. Cause: The national character set of the mining database was not a superset of the source database national character set.
Action: Perform the mining operation on a database having a compatible national character set. Cause: A session attribute was supplied which is invalid. Action: Re-issue with valid session attribute. Cause: A Logminer dictionary attribute was supplied which is invalid. Action: Re-issue with valid dictionary attribute.
Cause: A Logminer routine was called from the wrong state. 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.
Cause: Database does not have archivelog mode enabled. Action: Mount the database, then issue commands to enable archivelog mode. Cause: Compatibility mode set to some value less than 9. Action: Ensure that init.
Cause: Other users are performing DDL operations. Cause: Another processes is simultaneously attempting to run build ;. Action: Wait until the other processes completes.
Cause: The table may be missing, or locked by another user. Cause: No previously established Logminer Dictionary is available and a complete gather of a source system data dictionary was not found in the logstream.
Action: If build was not employed prior to this mining session the Logminer Ad Hoc user may elect to employ an alternate dictionary such as the current system catalog or a previously built flat file dictionary. Other Logminer clients must run build prior to mining. If build has been run, ensure that all logfiles which comprise the gathered system dictionary have beed added.
The following query, run on the system which build was run, can be helpful in identifying the requried files. Cause: The dictionary file or directory does not exist or is inaccessible. Action: Make sure that the dictionary file and directory exist and are accessible. Cause: The logfile has a different compatibility version then the rest of the logfile in the session".
Action: Make sure that the logfile has the same compatibility version as the rest of the logfiles in the session. Cause: Can not do this when other process is attached to LogMiner session. Cause: Unexpected result while accessing system catalog metadata. Cause: The LogMiner session requires more system resources than is currently available. Cause: Logmnr can not resume session because there is not enough SGA memory available to read in checkpointed data.
Logminer periodically checkpoints data to enable faster crash recovery. Cause: Log file is missing a range of scn values. Action: Verify the contiguity of the scn range reprented by the log files added to LogMiner. Cause: A coordinator process is already attached to the specified logminer context.
Action: Detach from the active coordinator session and retry the attach. Cause: A LogMiner client attempted to perform a privileged operation. Action: Issue the operation from the coordinator process. Note: If the primary reset log SCN is 0, then intermediary log files are missing.
Check the primary database for missing log files. In other scenarios, contact Oracle Support Services. Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data.
Action: Destroy this Logminer session. Re-enable supplemental log data on the source system and create a new LogMiner session. Cause: Invocation failed to specify a valid tablespace. Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. Action: First cause all Logminer sessions to be closed. Cause: An attempt was made to perform an operation that required that supplemental log data be enabled. Cause: The tables used by logminer are in the process of being moved to another tablespace.
Action: Wait until the move is complete and try again. Cause: Logminer sessions are currently active. Action: End all logminer sessions and retry. Cause: LogMiner ran out of space in the transaction queue. Cause: An attempt was made to mine a LogMiner dictionary from redo logs.
The version of the Oracle database that created the logs was higher than the Oracle database version that attempted to mine the logs. Action: Mine the logs using a newer version of the Oracle database having a version number that is equal to or greater than the dictionary version.
Cause: The database global name where the log file was generated did not match the user-specified global name of the Streams Capture process. Action: Start a new capture process and ensure that the user-specified global name matches that of the database that generated the log file. Cause: The specified input value for the parameter was not a valid number. Action: Specify a valid number and try again. Cause: NULL was specified for input value of parameter.
Cause: LogMiner reader process has completed mining of physical standby terminal logs up to the stop SCN. LogMiner reader is now waiting for logs from the new branch. Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. The builder process is now waiting for logs from the new branch to be registered before continuing. During terminal apply, LogMiner does not wait for logs to be registered.
It expects all logs between the starting point and the last log on any redo branch that it will or could mine through, to be present at the mining site. Action: Examine system.
Alternatively, do not use the FINISH APPLY clause, but if activating a logical standby, only do this when you are sure that the missing log files can not be located and registered as this can lead to data loss. Cause: specified restart scn is too old, logmnr could not find a proper checkpoint.
Action: Specify a bigger restart SCN to try again. Cause: One or more log files containing the LogMiner dictionary was not found. Action: Add into LogMiner all log files containing the dictionary. Cause: The number of processes requested by the caller can not be allocated. Action: Increase number of parallel servers allocated to the instance. Not enough memory has been set aside at instance startup to allocate the new LogMiner session.
Cause: A corrupt logfile has been recovered by RFS. Logical Standby should automatically restart. If logfile is still corrupt, may need to manually copy and reregister the logfile on the standby. Cause: The redo compatibility setting of the log file was unsupported by LogMiner.
Action: Specify a log file produced with a redo compatibility setting supported by LogMiner. Cause: One of the following occurred: 1 An attempt was made to create a file. Action: Create file or move file to the proper disk. Cause: One of the following occurred: 1 An attempt was made to switch to specified block size logs for all threads.
Action: Add log files to the thread that signals error, and try again. Cause: The database was migrated to use a specified log block size. Dropping all the logs specified would leave fewer than the required two log files with the specified block size per enabled thread. Action: Either drop fewer logs or disable the thread before deleting the logs.
It may be possible to clear the log rather than drop it. Cause: Log file was created on bigger sector disks, and moved to smaller sector disks. Action: Move the log file back to bigger sector disks. Cause: Log file was copied from smaller sector disks to larger sector native-mode disks. Action: Move the log file back to smaller sector disks. Cause: An attempt was made to automatically convert the control file created with maximum file name size value of to This could result in truncation of file names leading to loss of uniqueness among file names.
Cause: The value inserted was too large for the given column. Action: Do not insert a value greater than what the column can hold. Action: There was no data from the objects which may be due to end of fetch. Cause: The fetched column values were truncated. Action: Use the right data types to avoid truncation.
For non-unique indexes the rowid is considered part of the index key. Therefore, if you create an index nosort and two of the rows in the table have the same key and are stored in ascending order, but get split accross two extents where the dba of the first block in the second extent is less than the dba of the last block in the first extent, then the create index nosort may fail. Cause: Tried to fetch a column of size more than 64K and couldn't store the length of the column in the given indicator of size 2 bytes.
Action: Use the new bind type with call backs to fetch the long column. Cause: The user buffer bound by the user as packed decimal number contained an illegal value.
Cause: An attempt was made to bind an array without either a current array length pointer or a zero maximum array length. Cause: The query contains more distinct aggregates than can be processed. The current limit is Action: Reduce the number of distinct aggregate functions in the query. Cause: a. Action: Check that this is really what you want, then join b and c first in a view.
Cause: The number specified in exact fetch is less than the rows returned. Action: Rewrite the query or change number of rows requested. Action: Remove the escape character or specify the missing character. Action: Change it to a character string of length 1.
Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column. Action: commit or rollback transaction, and re-execute. Action: Remove the constraint s or do not perform the offending operation. Replace with a column name. Cause: Constants of different types are specified in an in-list. Action: Use constants of same type for in-lists. Cause: User is performing an array bind with a bind variable whose maximum size is greater than bytes.
Action: Such bind variables cannot participate in array binds. Use an ordinary bind operation instead. Cause: A bind variable of type 97 does not contain null at the last position. Cause: A bind variable of type 5 null-terminated string does not contain the terminating null in its buffer. Action: Terminate the string with a null character.
Action: Use one of the supported character sets. Action: Consult your manual for the maximum allowable length. The number of elements in the array and the current number of elements in the array cannot be more than the maximum size of the array. Cause: An impossible request for decimal to oracle number conversion was made.
Action: This conversion cannot be performed. Cause: String concatenation result is more than the maximum size. Action: Make sure that the result is less than the maximum size. Action: Specify a value within the proper range.
Cause: The specified table either does not exist or user does not have the proper privleges. Cause: The specified table does not have the proper field definitions. Previous Next JavaScript must be enabled to correctly display this content.
Action: Use a valid option. Action: Remove the alias. Action: Make sure that the cursor is open. ORA bind variables not allowed for data definition operations Cause: An attempt was made to use a bind variable in a SQL data definition operation.
ORA internal two task error Cause: Received send long message but don't have the cursor context. Action: Report as a bug. ORA insufficient privileges Cause: An attempt was made to perform a database operation without the necessary privileges. Action: Contact customer support. ORA maximum cursor memory exceeded Cause: Attempting to process a complex sql statement which consumed all available memory of the cursor. ORA insufficient privileges on underlying objects of the view Cause: Attempting to explain plan on other people's view without the necessary privileges on the underlying objects of the view.
ORA internal error. Action: Report as a bug ORA detaching a session with open cursors not allowed Cause: An attempt was made to detach a seesio n which had open cursors. ORA user side memory corruption [ string ], [ string ], [ string ], [ string ] Cause: The application code corrupted some of the usr memory used by oracle Action: Make sure that the application code is not overwriting memory.
ORA size string of buffer bound to variable exceeds maximum string Cause: An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. ORA Bind by name is not spupportted in streamed RPC Cause: A newer version of server is talking with this version requesting an operation not supported in this version.
ORA user storage address cannot be read ORA user storage address cannot be written ORA Object datatypes not supported for bind or define in this mode Cause: Bind or Define used for objects with an invalid mode Action: Change the mode. ORA invalid or ambiguous block. ORA cannot start up a V8 server using a V7 client application Cause: You are using an Oracle client application linked with version 7 or lower libraries and you attempted to start up a V8 or higher server.
ORA value of parameter " string " is inconsistent with that of other instances Cause: The value of the given parameter is required to be the same for all instances in the cluster database configuration.
ORA preceding errors in deferred rpc to " string. ORA savepoint ' string ' never established in this session or is invalid Cause: An attempt was made to roll back to a savepoint that was never established in this session, or was invalid. Disconnection forced Cause: The instance this process was connected to was terminated abnormally, probably via a shutdown abort. ORA database name ' string ' in control file is not ' string ' Cause: The database name in the control file does not match your database name.
ORA number of control files string does not equal string Cause: The number of control files used by this instance disagrees with the number of control files in an existing instance.
ORA mount is incompatible with mounts by other instances Cause: An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Action: See accompanying errors. Action: Mount the database. ORA database not open Cause: A command was attempted that requires the database to be open. Action: Open the database and try the command again ORA data file string : ' string ' Cause: Reporting file name for details of another error.
Action: See associated error message. ORA media recovery not started Cause: An attempt to continue media recovery is being made but media recovery was not started.
Action: None ORA file string needs media recovery Cause: An attempt was made to online or open a database with a file that is in need of media recovery. ORA IO error writing block to file string block string Cause: The device on which the file resides is probably offline. ORA IO error reading block from file string block string Cause: Device on which the file resides is probably offline Action: Restore access to the device ORA error in opening database file string Cause: Usually the file is not accessible.
Action: Restore the database file. ORA adding file ' string ' with illegal block size: string ; max limit is string ; min limit is string Cause: An attempt was made to add a database file with a block size that was greater than the maximum block size allowed or less than the minimum block size allowed or an invalid value that is, not power of 2 in the allowed range.
ORA cannot add any more database files: limit of string exceeded Cause: There is no more room in the control file for adding database files. ORA error in creating database file ' string ' Cause: Usually due to not having enough space on the device. ORA database file string failed verification check Cause: The information in this file is inconsistent with information from the control file.
ORA cannot start online backup; media recovery not enabled Cause: An attempt to start backup of an on-line tablespace failed because media recovery is not enabled. ORA cannot recover data file string - file is in use or recovery Cause: An attempt to do media recovery found that the file was not available for recovery. Action: Do not do media recovery. ORA cannot disable media recovery - file string has online backup set Cause: An attempt to disable media recovery found that an online backup is still in progress.
ORA user's default or temporary tablespace does not exist Cause: The user's default or temporary tablespace was dropped. ORA data file string is still in the middle of going offline Cause: It was not possible to get the lock for a file that is offline when attempting to bring it online.
ORA database must either be open in this instance or not at all Cause: The requested operation can not be done when the database is mounted but not open in this instance, and another instance has the database open. ORA error renaming data file string - new file ' string ' not found Cause: An attempt to change a data file's name in the control file failed because no file was found with the new name.
ORA cannot end online backup - none of the files are in backup Cause: None of the files were found to be in online backup when attempting to end an online backup. ORA cannot disable media recovery - file string needs media recovery Cause: An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled.
ORA File size string blocks exceeds maximum of string blocks Cause: Specified file size is larger than maximum allowable size value. Action: Specify a smaller size. ORA cannot start online backup - file string is already in backup Cause: When starting an online backup it was noticed that an online backup was already started for one of the data files. Action: Bring the file online. ORA cannot refresh file size for datafile string Cause: An operating system or device error occurred when retrieving the file's size.
Action: Restore access to the device. ORA cannot shutdown - file string has online backup set Cause: An attempt to shutdown normally found that an online backup is still in progress. ORA cannot prevent writes - file string has online backup set Cause: An attempt to make a tablespace read only or offline normal found that an online backup is still in progress. ORA use media recovery to recover block, restore backup if needed Cause: Error occurred.
ORA file string was not restored from a sufficiently old backup Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the database consistent. ORA an incompatible media recovery is active Cause: Attempted to start an incompatible media recovery or open resetlogs during media recovery or RMAN backup. ORA the database is being opened, closed, mounted or dismounted Cause: The requested operation needs the instance to be in a particular state but the state is being changed.
ORA recovery or flashback in progress may need access to files Cause: Either media recovery, instance recovery, or flashback was in progress.
ORA database string already mounted Cause: Another instance has a database by this name mounted. ORA physical block size string does not match size string of other members Cause: The file is located on a device with a different physical block size than the other members in the group Action: Use a physical device with matching block size. Action: Upgrade the server. Action: Start Oracle. ORA fatal connection error: unrecognized call type Cause: An illegal internal operation was attempted.
Action: Log off before shutting down Oracle. ORA you are currently logged on Cause: An attempt was made to log on while already logged on. ORA multiple logons per process not yet supported Cause: Oracle does not support multiple logons per process. ORA background process initialization failure Cause: A failure occurred during initialization of the background processes. ORA failure in processing system parameters Cause: Failure during processing of initialization parameters during system startup.
Action: Further diagnostic information should be in the error stack. Action: Shut down Oracle first, if you want to restart it. ORA file or set it to "default" or "intent". ORA value of parameter " string " is inconsistent with that of other instances Cause: The value of the given initialization parameter is required to be the same for all instances in the cluster database configuration.
ORA preceding errors in deferred rpc to " string. Action: Correct the cause of the preceding errors. ORA savepoint ' string ' never established Cause: An attempt was made to roll back to a savepoint that was never established. Action: No action is required. Action: Log off. Action: Wait for the instance to restart or contact the database administrator. ORA program version string incompatible with instance string Cause: The program was linked with a different version of the server than the instance to which it is attempting to connect.
ORA cannot shutdown while in a transaction - commit or rollback first Cause: An attempt was made to shut down the database while a transaction was in progress. Action: Retry the insert or update. ORA database already mounted Cause: An attempt was made to mount a database with the name of a currently mounted database.
ORA database being created currently mounted by some other instance Cause: Some other instance has the database of same name currently mounted and you are trying to create it.
Action: Either change the database name or shut down the other instance. Action: Shut down the other instance or mount in a compatible mode. ORA database name ' string ' in controlfile is not ' string ' Cause: The database name in the control file does not match your database name. Action: Either find the correct control file or change your database name. ORA number of controlfiles string does not equal string Cause: The number of control files used by this instance disagrees with the number of control files in an existing instance.
Action: Check to make sure that all control files are listed. ORA mount is incompatible with mounts by other instances Cause: An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible.
Action: See accompanying errors. ORA database must be closed before dismounting Cause: An attempt was made to dismount a database before it was closed. Action: Close the database, then retry the operation. ORA database must be mounted for media recovery Cause: An attempt to perform media recovery was made but the database is not mounted. Action: Mount the database. Action: Complete or cancel the media recovery session or backup. ORA database not open Cause: A command was attempted that requires the database to be open.
Action: Open the database and try the command again. ORA data file string : ' string ' Cause: This message reports the file name involved with other messages. Action: See the associated messages for a description of the problem. ORA media recovery not started Cause: An attempt to continue media recovery is being made but media recovery was not started. ORA file string needs media recovery Cause: An attempt was made to open a datafile that is in need of media recovery.
ORA IO error writing block to file string block string Cause: The device on which the file resides is probably offline. ORA IO error reading block from file string block string Cause: The device on which the file resides is probably off line. Action: Restore access to the device, then retry the operation. ORA error in opening database file string Cause: Usually the file is not accessible. ORA adding file ' string ' with illegal block size: string ; limit is string Cause: An attempt was made to add a datafile with a block size that is greater than the maximum block size allowed.
Action: Retry the operation with a smaller block size. ORA cannot add any more database files: limit of string exceeded Cause: An attempt to add a datafile failed because the limit for such files had already been reached. ORA error in creating database file ' string ' Cause: Insufficient space on device. ORA cannot remove online database file string Cause: An attempt was made to drop a datafile when it is online. Action: Take file offline before dropping.
Action: Close database in all instances and end all recovery sessions. ORA database file string failed verification check Cause: The information in this file is inconsistent with information from the control file. ORA cannot start online backup; media recovery not enabled Cause: An attempt to start backup of an online tablespace failed because media recovery is not enabled.
Action: Enable media recovery and retry this operation. ORA cannot recover data file string - file is in use or recovery Cause: An attempt to do media recovery found that the file was not available for recovery.
Action: Do not do media recovery. ORA cannot disable media recovery - file string has online backup set Cause: An attempt to disable media recovery found that an online backup is still in progress.
Action: End the backup of the offending tablespace and retry this command. Action: Shut down Oracle and mount the database in exclusive mode.
ORA database name ' string ' exceeds size limit of string characters Cause: The specified database name is too long. ORA cannot start online backup - file string is offline Cause: An attempt to start an online backup found that one of the files is offline.
ORA user's default or temporary tablespace does not exist Cause: The user's default or temporary tablespace was dropped. Action: Reassign the default or temporary tablespace. ORA length of database file name ' string ' exceeds limit of string characters Cause: The specified datafile name is too long. Action: Shorten the file name and retry the operation. ORA length of log file name ' string ' exceeds limit of string characters Cause: The specified redo log file name is too long.
ORA database mounted exclusive by another instance Cause: An attempt to access a database failed because it is mounted in exclusive mode by another instance. Action: Bring the datafile back online.
Action: Create the file with a larger size. ORA data file string is still in the middle of going offline Cause: It was not possible to get the lock for a file that is offline when attempting to bring it online. Action: Wait for the other instance to release the lock on the file. ORA database must either be open in this instance or not at all Cause: The requested operation cannot be done when the database is mounted but not open in this instance, and another instance has the database open. ORA cannot end online backup - all files are offline Cause: All the files were found to be offline when attempting to end an online backup.
ORA error renaming data file string - new file ' string ' not found Cause: An attempt to change a datafile's name in the control file failed because no file was found with the new name. ORA cannot end online backup - none of the files are in backup Cause: None of the files were found to be in online backup when attempting to end an online backup.
ORA cannot disable media recovery - file string needs media recovery Cause: An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled. ORA File size string blocks exceeds maximum of string blocks Cause: Specified file size is larger than maximum allowable size value. Action: Specify a smaller size. ORA cannot start online backup - file string is already in backup Cause: An attempt was made to start an online backup, but an online backup was already started for one of the datafiles.
Action: End the first backup before beginning another. Action: Bring the file online. ORA cannot shutdown - file string has online backup set Cause: An attempt to shut down normally found that an online backup is still in progress. ORA cannot prevent writes - file string has online backup set Cause: Tablespace cannot be taken offline or made read-only when online backup is running.
ORA use media recovery to recover block, restore backup if needed Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. ORA file string was not restored from a sufficiently old backup Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent.
ORA an incompatible media recovery is active Cause: Attempted to start an incompatible media recovery or open resetlogs during media recovery or RMAN backup. ORA database busy. Open, close, mount, and dismount not allowed now Cause: Some operation is in progress that expects the state of the instance to remain open or mounted. ORA the database is being opened, closed, mounted or dismounted Cause: The attempted operation will not succeed while the instance is in one of the states mentioned in the message.
ORA recovery in progress may need access to files Cause: Either media or instance recovery is in progress. Action: Wait for the recovery to complete and try again. ORA database string already mounted Cause: Another instance has a database by this name mounted. Action: Check the mentioned file.
ORA database name string in file header does not match given name of string Cause: The database name given at the command line does not match the database name found in the file header. Action: Specify the correct file name and size in bytes.
Action: Increase the maximum specified on the command line. ORA physical block size string does not match size string of other members Cause: The file is located on a device with a different physical block size than the other members in the group. Action: Use a physical device with matching block size.
ORA datafile string going offline due to error advancing checkpoint Cause: The checkpoint in the file header could not be advanced. ORA recovery of thread string stuck at block string of file string Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. ORA data dictionary indicates missing data file from system tablespace Cause: One of the following: The database is recovered to a point in time in the future of the control file.
Action: One of the following: Recover the database from a more recent control file. Re-create the control file, ensuring all datafiles are included for the system tablespace in the command line. ORA data dictionary has more than the string files allowed by the instance Cause: The data dictionary is found to have more files than that which can be supported by this instance.
ORA file string does not exist Cause: During datafile recovery, a file was listed that was not part of the database. Action: Recover file from a backup or re-create the database. Action: Shut down the other instance and then mount shared. Action: Specify a correct log file number. ORA file string failed verification tests Cause: The datafile did not pass the checks to insure it is part of the database.
ORA cannot read from file string because it failed verification tests Cause: The datafile did not pass the checks to insure it is part of the database. Action: Restore file from a more recent backup. ORA file string is already offline - cannot do a normal offline Cause: When attempting to do a normal tablespace offline, it was discovered that one of the files in the tablespace was already offline. ORA file string is not the same file seen at start of recovery Cause: A different copy of the file was accessed the last time media recovery looked at the file header.
Action: Ensure the correct file is available, and then retry recovery. ORA file string needs more recovery to be consistent Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent.
ORA online backup of file string needs more recovery to be consistent Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. ORA file string is inconsistent due to a failed media recovery session Cause: The file was being recovered but the recovery did not terminate normally.
Action: Resubmit the command with the appropriate log file size. ORA file string is not in online backup mode Cause: An attempt was made to end an online backup for a file that is not in online backup. Action: Do not enter command since it is not needed. ORA actual file size of string is smaller than correct size of string blocks Cause: The size of the file as returned by the operating system is smaller than the size of the file as indicated in the file header and the control file.
Action: Restore a good copy of the datafile and do recovery as needed. ORA 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. Action: Restore a current copy of the datafile and do recovery as needed. ORA file number is string rather than string - wrong file Cause: The file number in the file header is not correct. Action: Restore a copy of the correct datafile and do recovery as needed.
ORA not a data file - type number in header is string Cause: The file type in the header is not correct for a datafile. ORA 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.
ORA file is more recent than controlfile - old controlfile Cause: The control file change sequence number in the datafile is greater than the number in the control file. ORA 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. ORA data file header is media corrupt Cause: The file header block is internally inconsistent.
ORA logfile member is not from the same point-in-time Cause: A member of a multiple-member log file group is from a different point in time. ORA 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.
ORA data file string is not the same file to a background process Cause: When the database writer opens the datafile, it is accessing a different physical file than the foreground doing the recovery.
ORA 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. Action: Find the correct log member or omit this member from the command. ORA 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 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. ORA cannot start online backup - file string is read only Cause: An attempt to start an online backup found that one of the files is marked read only. Action: Make the backup without the begin backup command. ORA file string is read only - cannot recover using backup controlfile Cause: An attempt to do media recovery using a backup control file found that one of the files is marked read only.
ORA cannot end backup of file string - file is in use or recovery Cause: An attempt was made to end an online backup of file when the file is busy. ORA Error string occurred during initialization of file header access Cause: The indicated error occurred while doing initialization processing of file headers. ORA 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 cannot shrink datafile string Cause: An operating system error occurred during the resize.
Action: The error is ignored, operation continues normally. ORA too many data files to add in one command Cause: The command specifies adding more datafiles than can be done in one command.
ORA an external cache has died Cause: The external cache may have been restarted. ORA system tablespace file suffered media failure Cause: A system tablespace file was detected as inaccessible due to media failure. ORA unnamed datafile s added to controlfile 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.
ORA 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. Action: Restore more recent backups and recover them. ORA archiving not allowed in a clone database Cause: An attempt was made to archive an online redo log or enable archiving for a clone database. ORA Error string occurred during termination of file header access Cause: The indicated error occurred while terminating the processing of file headers.
Action: The indicated error should be corrected. ORA Unknown File Header Version read for file number string Cause: Read of the file header returned a record but its version cannot be identified. ORA 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. ORA cannot start online backup - file string in recovery manager backup Cause: The specified file is being backed up by Recovery Manager.
ORA cannot end online backup - file string in recovery manager backup Cause: The specified file is being backed up by Recovery Manager. ORA cannot shutdown - file string in recovery manager backup Cause: An attempt to shut down normally found that a Recovery Manager backup is still in progress. ORA 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 cannot reuse database file string , unknown file size Cause: The size of the raw partion cannot be determined. ORA 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 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. Action: Internal error - contact Oracle Support Services. ORA 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.
ORA cannot add datafile ' string ' - file could not be created Cause: Automated standby file management was enabled but an added file could not automatically be created on the standby.
ORA Operation string is not allowed if standby file management is automatic. ORA Cannot add file string. File has an Oracle Managed Files file name. Action: Retry the operation with a new file name. Action: Check the error stack for more detailed information. The start or the end SCN may not be available in the log files selected.
The dictionary file specified may be from a different database than the one that generated the log files. LogMiner may have encountered an internal error from which it cannot recover. Action: Specify a valid SCN range. Action: Specify a valid date range. Action: Specify valid Options. ORA file string cannot be opened Cause: The specified file cannot be opened. Action: Check to make sure the file or directory exists and is accessible. ORA error reading file string Cause: The file or directory may not exist or is inaccessible.
Action: Specify a log file produced by the same database. ORA file string is from a different database incarnation Cause: The logfile was produced by a different incarnation of the database. Action: Add a logfile that is produced by the same incarnation. ORA file string is from a different database incarnation Cause: The logfile is produced by a different incarnation of the database. ORA cannot add duplicate logfile string Cause: The log file specified has already been added to the list of log files.
Action: Specify a different log file. ORA cannot remove unlisted logfile string Cause: The user attempted to remove a log file that is not present in the list.
Action: Specify a valid logfile. ORA missing logfile Cause: Not all logfiles corresponding to the data or scn range specified have been added to the list. Action: Specify at least one log file. ORA error occurred while processing information in dictionary file string , possible corruption Cause: The dictionary file is corrupt.
Action: Get a new dictionary file. Action: Specify a compatible dictionary file. ORA character set mismatch between dictionary string and logfiles Cause: The character set of the database that produced the dictionary file is different from the character set of the database that produced the log files. Action: Specify a dictionary file with the same character set. ORA 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: Get a correct dictionary materialized view. ORA dictionary string corresponds to a different database incarnation Cause: The dictionary file was extracted from a different incarnation of the database. ORA syntax error in logmnr. Action: Use correct syntax. ORA schema string , specified in logmnr. Action: Specify a correct schema or a compatible dictionary file. ORA table string , schema string , specified in logmnr. Action: Make sure that the table specified is valid.
ORA column string , specified in logmnr. Action: Make sure that the column specified is valid. Action: Use a valid Logminer session ID or session handle. ORA 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: Attach to a Logminer session before issuing the command or procedure. ORA Logminer session not started Cause: Logminer activate session was called before prepare session.
Action: Re-issue with a valid session attribute. Action: Re-issue with a valid dictionary attribute. Action: Re-issue with a valid table name. Action: Specify a logfile produced by the same database. ORA archive log mode must be enabled to build into the logstream Cause: The database does not have archivelog mode enabled. ORA only one build operation may occur at one time Cause: Another process is simultaneously attempting to run build.
Action: Wait until the other process completes. ORA unable to truncate required build table Cause: The table may be missing or locked by another user. Action: Check the trace file. ORA failed to establish Logminer Dictionary Cause: No previously established Logminer Dictionary is available and a complete gather of a source system data dictionary was not found in the logstream.
ORA log file has a different compatibility version Cause: The logfile has a different compatibility version than the rest of the logfiles in the session. ORA logfile is too old Cause: An attempt was made to add an already processed logfile.
ORA LogMiner out-of-memory Cause: The logfiles to be analyzed in the current LogMiner session require more system resources than what is currently available. ORA LogMiner can not resume session due to inability of staging checkpointed data Cause: Logminer can not resume session because there is not enough SGA memory available to read in checkpointed data.
ORA LogMiner coordinator already attached Cause: A coordinator process is already attached to the specified logminer context. Action: Detach from the active coordinator session and retry the attach.
ORA Supplemental log data must be enabled to build into the logstream Cause: Supplemental log data must be enabled on this database instance. Action: Enable supplemental log data. ORA Dependent LogMiner sessions relying on supplementally logged data exist Cause: LogMiner sessions exist on this database instance which rely on the existence of supplemental log data. ORA Supplemental log data no longer found Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data.
ORA must specify a tablespace name Cause: Invocation failed to specify either a dictionary tablespace or a spill tablespace. Action: Specify a bigger restart SCN to try again. Action: Add into LogMiner all log files containing the dictionary. ORA Insufficient processes for specified LogMiner operation Cause: The number of processes requested by the caller can not be allocated.
Action: Increase the number of parallel servers allocated to the instance. ORA inserted value too large for column Cause: The value entered is larger than the maximum width defined for the column. ORA no data found Cause: In a host language program, all records have been fetched.
This is the simplest solution. Use an indicator to record the presence of the NULL. You probably should use this option when you want a specific action to be taken when a NULL arises. Revise the cursor definition so that no columns possibly containing NULL values are retrieved. ORA cannot store the length of column in the indicator Cause: An attempt was made to fetch a column of size more than 64K and could not store the length of the column in the given indicator of size 2 bytes.
0コメント