Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: ULIMIT system call returned an error.
Action: Check errno.
Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages.
Action: Check additional return error for more information.
Cause: CREATE() failed when trying to create the TASDEF file.
Action: Verify permissions on $(ORACLE_HOME)/dbs directory.
Cause: Unable to open tasdef@.dbf file.
Action: Check errno. Possible permission problem. Verify that tasdef@.dbf file exists.
Cause: Read system call returned an error when attempting to read ?/dbs/tasdef@.dbf.
Action: Check errno returned. SGADEF file may be corrupted or incompatible with Oracle version.
Cause: Write call failed.
Action: Check errno returned. Possibly out of space on device.
Cause: Close system call returned an error.
Action: Check errno returned. Possible operating system failure.
Cause: Error in SHMGET.
Action: Check errno returned. Verify that enough shared memory is available on the system.
Cause: Error in SHMAT.
Action: Check errno returned.Verify that enough shared memory is available on the system.
Cause: Error in SHMAT.
Action: Check errno returned.Verify that enough shared memory is available on the system.
Cause: Error in SHMDT.
Action: Check errno returned.
Cause: Error in SHMDT.
Action: Check errno returned.
Cause: Error in SHMCTL.
Action: Check errno returned.
Cause: The ORATAB file does not exist.
Action: Install Oracle before you use it or re-create the ORATAB file.
Cause: You are trying to start Oracle on another PU than you configured Oracle on or there is no entry for this SID in the ORATAB file.
Action: Start Oracle with this SID on its designated PU (see the ORATAB file). Or install the new database with SID.
Cause: The TXIPC driver failed to create pipes for two-task communications with the Oracle shadow process.
Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator.
Cause: Failure of sltln(txipc@.trc) while creating debug channel.
Action: Check additional return error for more information.
Cause: The TXIPC driver failed to create channels for two-task communications with the Oracle shadow process.
Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table operating system error code and contact your system administrator.
Cause: The TXIPC driver could not access the Oracle executable.
Action: Check the permissions on the Oracle executable and each component of the ORACLE_HOME/bin path.
Cause: The TXIPX driver failed to allocate enough heap space for its context area buffers.
Action: Contact Oracle Support Services.
Cause: The system call GETHOSTNAME returned an error. This is most likely an internal error.
Action: Make sure GETHOSTNAME is successful in other contexts, and if so contact Oracle Support Services.
Cause: Memory needed for a temporary buffer could not be allocated. The additional information field contains the number of bytes that Oracle attempted to allocate.
Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Support Services.
Cause: No entry exists for the user in the Oracle password file.
Action: Have the database administrator install a password entry by running ORAPASSWD.
Cause: The password entered by the user was incorrect.
Action: Enter the correct password.
Cause: Oracle was unable to allocate memory for one or both of the buffers that are used to hold the name of DBA and the operator users.
Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to allocate memory for the user name that is to be used in the encryption of the user's password.
Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Support Services.
Cause: Oracle could not open the password file for reading.
Action: Check the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running ORAPASSWD. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact Oracle Support Services.
Cause: Oracle was unable to encrypt a password. This is an internal error.
Action: Contact Oracle Support Services.
Cause: A user attempted to connect as "internal," but did not specify a password.
Action: Connect as internal again and specify a password.
Cause: Oracle was unable to retrieve the user's privilege set from the SQL*Net connection.
Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to set the label of the dedicated to server to the required value.
Action: Check the UNIX error number for a possible operating system error. Also, check the privileges on the Oracle executable. It should have at least ALLOWMACACCESS privilege.
Cause: Oracle was unable to retrieve the user's sensitivity label from the SQL*Net connection.
Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to retrieve the user's information label from the SQL*Net connection.
Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to spawn a background process because the directory that will hold trace files of the background processes was not created properly.
Action: Examine the directory pointed to by the initialization parameter BACKGROUND_DUMP_DEST. Make sure that all of the following is true:
Cause: Oracle was unable to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly.
Action: Examine the directory pointed to by the initialization parameter USER_DUMP_DEST. Make sure that all of the following is true:
Cause: Oracle was unable to spawn a background process because the directory that holds the core dumps produced by Oracle processes in the event of exceptions was not created properly.
Action: Examine the directory pointed to by the initialization parameter CORE_DUMP_DEST. Make sure that all of the following is true:
Cause: Oracle was not able to create the file being used to hold audit trail records.
Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
Cause: A dedicated server was unable to set it's own privilege set.
Action: Check the privileges granted to the Oracle executable. It must have at least ALLOWMACACESS privilege.
Cause: Oracle was not able to set the label of a server to a new value.
Action: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it has ALLOWMACACCESS privilege.
Cause: Oracle was unable to restore the label of the server to the value that it had before raising it to database high. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The result of a greatest lower bound operation on two labels was not valid.
Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.
Cause: The result of a least upper bound operation on two labels was not valid.
Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.
Cause: An attempt to open a password file for reading failed.
Action: Make sure that the permissions on the file have not been changed so that the Oracle user cannot open it.
Cause: An attempt to close a password file failed.
Action: Check the UNIX error number for the specific reason.
Cause: The removal of the old password file failed.
Action: Check the UNIX error number for the specific reason.
Cause: Oracle was unable to create a link so that the old password file could be saved.
Action: Check the UNIX error number for the specific reason.
Cause: Oracle was unable to complete the saving of the current password file.
Action: Check the UNIX error number for the specific reason.
Cause: Oracle was unable to create a password file.
Action: Check the UNIX error number for the specific reason.
Cause: Oracle was unable to change a password file to be read only.
Action: Check the UNIX error number for the specific reason.
Cause: Oracle was unable to save the previous values of selected signal handlers. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Oracle was unable to restore the previous values of selected signal handlers. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The header of one of the password files was not in the format that Oracle expected.
Action: Check the headers of both files. The header should be in the format "FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N" where N is a number. Remove the corrupt file(s) and re-run ORAPASSWD.
Cause: The version of ORAPASSWD or installer that is being run is older than that of the Oracle password file. Since the file version is only changed when the format is changed, this error means that the executable is using a different format than that with which the file was created.
Action: Run a version of the installer or ORAPASSWD whose version is the same or later than that of the file.
Cause: The attempt to write out the header of the Oracle password file failed.
Action: Check the operating system error number. It is possible that the file system became full.
Cause: When it is building a list of password file entries, Oracle allocates memory for various components. One of the allocations failed.
Action: Check the operating system error number. The system has probably run out of memory.
Cause: An entry in an Oracle password file was not in the format that Oracle expected.
Action: Removed the corrupt file(s) and re-run ORAPASSWD.
Cause: Oracle was unable to write header information to the file being used as the audit trail.
Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
Cause: The buffer that was to be used to hold a file name was determined to be too short for the generated name. This will happen if the translated name for either a trace file or an audit file is longer than the maximum allowed, which on many ports is 256 characters.
Action: Use a shorter file name.
Cause: Oracle was not able to allocate the memory needed to hold the attributes of the SQL*Net connection. The "Additional Information" field holds the number of bytes that Oracle attempted to allocate.
Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to get the information label for a process.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to get the operating system privileges for the client process.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to get its privileges from the operating system.
Action: This is an error that should never happen. Contact Oracle Support Services.
Cause: Oracle was unable to create a file.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: The Distributed Lock Manager returned an unexpected value.
Action: Check for system error message and refer to the Distributed Lock Manager documentation or contact Oracle Support Services.
Cause: The Distributed Lock Manager returned an unexpected value.
Action: Check for Lock Manager error messages and refer to the Distributed Lock Manager documentation or contact Oracle Support Services.
Cause: The Distributed Lock Manager returned an unexpected value.
Action: Check for Lock Manager error messages and refer to the Distributed Lock Manager documentation or contact Oracle Support Services.
Cause: DLM system service x returned an unexpected value.
Action: Check for system error message and refer to the Distributed Lock Manager documentation or contact Oracle Support Services.
Cause: A global locking system service returned an unexpected value.
Action: Check for system error message (if any) and refer to refer to the Distributed Lock Manager documentation or contact Oracle Support Services.
Cause: The attempt to send a termination signal to IMON failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The IMON process was unable to add an entry for a server process because another active process occupies the slot. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The IMON process was unable to delete a server process from its process ID array because no entry for the process could be found. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Oracle was unable to set up a handler for the signal used to notify it that the instance was shutting down. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Oracle failed to set the handler for the termination signal to its previous value. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Failure of SLTLN in SCUMNT.
Action: Check additional returned error for more information.
Cause: Open system call returned an error.
Action: Check errno.
Cause: Lock file operating system call returned an error.
Action: Check errno.
Cause: Close system call returned an error.
Action: Check errno.
Cause: The process was unable to initialize the SDI channel properly.
Action: Correct the operating system error and retry the operation.
Cause: The process was unable to attach to the SDI channel.
Action: Verify that the SDI process specific limits correctly configured. Correct the operating system error and retry the operation.
Cause: The process was unable to create a communications endpoint.
Action: Verify that the SDI port specific limits correctly configured. Correct the operating system error and retry the operation.
Cause: The process was unable to connect to another endpoint.
Action: Verify that the SDI port specific limits correctly configured. Check that the other node(s) is part of the cluster and operating properly. Correct the operating system error and retry the operation.
Cause: The process was unable to disconnect cleanly from another endpoint.
Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.
Cause: The process was unable to send a message to an existing endpoint.
Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.
Cause: The process encountered an error while trying to receive a message.
Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.
Cause: The process was unable to add a page to the SDI buffer pool.
Action: Correct the operating system error and retry the operation.
Cause: The process was unable to remove a page to the SDI buffer pool.
Action: Correct the operating system error and retry the operation.
Cause: The process was unable to shut down the SDI channel.
Action: Check the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance.
Cause: File does not exist or is not accessible.
Action: Restart the instance to create the SGA definition file.
Cause: UNIX read() operation failed.
Action: Check errno and take appropriate action.
Cause: Struct SKGMSDEF size differs from the number of bytes read from the SGA file.
Action: Compare the two struct definitions and ensure that they are identical in size and structure.
Cause: The instance is not up, or SGA segments are not read-accessible.
Action: Verify that the instance is up and read permissions for the SGA segments are set.
Cause: SKGMSDEF struct is corrupted and/or segment addresses are modified.
Action: Safely shut down the instance and mount the SGA segments again.
Cause: Pointer to SKGMSDEF struct used without validating it.
Action: Assign a valid address to the SKGMSDEF struct pointer before using it.
Cause: Report block type for details of another error.
Action: See associated error message.
Cause: Report block type and data object number for details of another error.
Action: See associated error message.
Cause: See other errors on error stack.
Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.
Cause: Test recovery completed.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery.
Cause: Report tablespace name for details of another error.
Action: See associated error message.
Cause: There can only be one test recovery session at any time. Another test recovery session is active.
Action: Wait until the other test recovery session completes.
Cause: Test recovery tests redo in memory. It can no longer proceed because it has consumed all the memory it can use.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.
Cause: There are two possible causes of this error:
Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.
Cause: Out of SGA memory.
Action: Restart the instance. If the problem persists, then contact Oracle Support Services.
Cause: Test recovery completed.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.
Cause: User canceled test recovery.
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery.
Cause: See other errors on the error stack.
Action: See other messages on the error stack. It is possible that no action is needed. See other messages on error stack for a summary of the result of the test recovery so far.
Cause: This message shows the range of test recovery that has been tested.
Action: No action is needed. See other messages on the error stack.
Cause: This message summarizes test recovery result.
Action: No action is needed. See other messages on the error stack.
Cause: There was not enough memory to restore recovered datafiles to consistent state.
Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.
Cause: See alert file or other errors on the stack for a cause of the problem.
Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.
Cause: Test recovery option is used for managed standby database recovery.
Action: Either remove the test recovery option or invoke manual test standby database recovery.
Cause: You used the allow corruption option for managed standby database recovery.
Action: Either remove the allow corruption option or invoke manual standby database recovery.
Cause: To proceed with recovery, test recovery needs to modify the control file. But test recovery is not allowed to modify the controlfile.
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
Cause: To proceed with recovery, test recovery needs to modify a datafile header. But test recovery is not allowed to modify datafile headers.
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
Cause: To proceed with recovery, test recovery needs to modify a redo log header. But test recovery is not allowed to modify redo log headers.
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
Cause: User requested backup control file test recovery, but the control file is not a backup control file.
Action: Use a backup control file, or do not use the USING BACKUP CONTROLFILE option.
Cause: One of the files to be recovered is renamed as missing.
Action: Rename the file to the correct file or offline it.
Cause: Both test recovery and parallel recovery are requested.
Action: Drop either one of the two recovery options.
Cause: Test recovery has encountered a special redo that may modify control file.
Action: No action is needed. Test recovery has proceeded successfully as far as it could from its starting point.
Cause: This message summarizes test recovery result: Oracle may have to corrupt one block in order to apply the range of redo tested.
Action: See the alert log for details of the problem.
Cause: The number specified in the ALLOW n CORRUPTION option is too big.
Action: Use a smaller number.
Cause: The number specified in the ALLOW n CORRUPTION option is too big.
Action: Change to allow zero or one corruption.
Cause: This message summarizes test recovery result: Oracle may have to corrupt a number of data blocks as specified in the message in order to apply the range of redo tested.
Action: See the alert log for details of the problems.
Cause: This procedure can be used only on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT.
Action: Recheck the segment name and type and re-issue the statement.
Cause: Tablespace with AUTO SEGMENT SPACE MANAGEMENT specified cannot be used as a temporary tablespace.
Action: Recheck the tablespace name and re-issue the statement.
Cause: Cannot perform the operation on tablespace with AUTO SEGMENT SPACE MANAGEMENT.
Action: Recheck the tablespace name and re-issue the statement.
Cause: Rollback segments cannot be created in dictionary managed tablespaces when the SYSTEM tablespace is locally managed.
Action: Recheck the tablespace name and re-issue the statement.
Cause: This DBMS_SPACE operation is not permitted on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT.
Action: Recheck the segment name and type and re-issue the statement.
Cause: Cannot alter freelist storage parameter for segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT.
Action: Recheck the segment name and re-issue the statement.
Cause: The specified file number and block number of the data block does not belong to the segment.
Action: Recheck the segment, file number, block number and re-issue the statement.
Cause: The SYSTEM tablespace is being migrated to locally managed format.
Action: Re-issue this command once SYSTEM tablespace migration is complete.
Cause: SYSTEM tablespace migration requires rollback segment in locally managed tablespace.
Action: Drop rollback segments in dictionary managed tablespaces other than SYSTEM and create rollback segments in locally managed tablespace. Then retry migration.
Cause: When SYSTEM tablespace is migrated, found rollback segments in dictionary managed tablespaces.
Action: Drop the rollback segments in dictionary managed tablespaces and re-issue the command.
Cause: When SYSTEM tablespace is being migrated, database should be mounted in Exclusive mode and in Restricted mode.
Action: Re-issue this command after mounting the database in the correct mode.
Cause: When SYSTEM tablespace is being migrated, no user should have SYSTEM as the default temporary tablespace.
Action: Re-issue this command after altering the default temporary tablespace setting for all users.
Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend recursively more than 1000 times.
Action: If SYSTEM tablespace is very large, then simply reissue the tablespace migration command.
Cause: When SYSTEM tablespace is being migrated, tablespaces other than the three should be ALTERed to read only.
Action: Alter the tablespace status to read only and retry migration.
Cause: The specified dba is not valid.
Action: Check if the specified dba belongs to the segment and is under the segment HWM and re-issue the statement.
Cause: An attempt was made to create a materialized view log on a table that already has a materialized view log. Each master table can have only one materialized view log.
Action: All materialized views on a table can use the same materialized view log for that table. To make changes to the existing log, use the ALTER MATERIALIZED VIEW LOG command or drop the materialized view log and create it again.
Cause: Materialized view logs are filled by a trigger on the master table. That trigger cannot be created.
Action: To create a materialized view log, drop the current trigger on the master.
Cause: There was no materialized view log on the master table.
Action: Create a materialized view log on the master table.
Cause: The materialized view with the given owner and name does not exist.
Action: Verify inputs and create a materialized view.
Cause: The materialized view log does not exist or cannot be used.
Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log, REFRESH FAST will be available starting the next time the materialized view is refreshed.
Cause: An attempt was made to schedule an automated materialized view refresh for a time in the past.
Action: Choose a time in the future instead.
Cause: An attempt was made to create a materialized view with the name of an existing materialized view.
Action: Create the materialized view using a different name or drop the existing materialized view.
Cause: The CREATE MATERIALIZED VIEW .. or CREATE MATERIALIZED VIEW LOG .. REUSE command was given inconsistent parameters immediately after the REUSE.
Action: Examine the other messages on the stack to find the problem.
Cause: Table SNAP$_mview_name reads rows from the view MVIEW$_mview_name, which is a view on the master table (the master may be at a remote site). Any error in this path will cause this error at refresh time. For fast refreshes, the table master_owner.MLOG$_master is also referenced.
Action: Examine the other messages on the stack to find the problem. See if the objects SNAP$_mview_name, MVIEW$_mview_name, mowner.master@dblink, mowner.MLOG$_master@dblink still exist.
Cause: An attempt was made to create a materialized view with a long column.
Action: Do not attempt to create materialized view logs with long columns.
Cause: An attempt was made to create a materialized view log on the table owned by SYS. CREATE MATERIALIZED VIEW LOG attempts to create a trigger on the table, but triggers can not be created on SYS tables.
Action: Do not create a materialized view log on SYS tables.
Cause: An error was caught in dbms_ijob.run from one or more jobs which were due to be run.
Action: Look at the alert log for details on which jobs failed and why.
Cause: Some kind of error was caught while doing an automatic execute of a job.
Action: Look at the accompanying errors for details on why the execute failed.
Cause: The updatable materialized view query contained a join, subquery, union, connect by, order by, or group by clause.
Action: Make the materialized view simpler. If a join is really needed, make multiple simple materialized views then put a view on top of them.
Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the WITH PRIMARY KEY option and the master table did not contain a primary key constraint or the constraint was disabled.
Action: Reissue the command using only the WITH ROWID option, create a primary key constraint on the master table, or enable an existing primary key constraint.
Cause: Neither ROWIDs nor primary key constraints are supported for complex queries.
Action: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE option or create a simple materialized view.
Cause: The query that instantiates the materialized view did not include all of the columns in the master's primary key constraint.
Action: Include all of the master's primary key columns in the materialized view query or create a ROWID materialized view.
Cause: An attempt was made to convert the primary key of a materialized view to a ROWID materialized view.
Action: Conversion of a primary key materialized view to a ROWID materialized view is not supported. Create a new materialized view with ROWIDs or drop and recreate the materialized view with ROWIDs.
Cause: The refresh operations for the indicated materialized view could not be regenerated due to errors.
Action: Correct the problem indicated in the following error messages and repeat the operation.
Cause: An attempt was made to create a materialized view or a materialized view log on a remote synonym which is unsupported.
Action: Do not create a materialized view or materialized view log on a remote synonym.
Cause: An attempt was made to unregister a materialized view that is not registered.
Action: No action required.
Cause: The indicated materialized view is no longer valid.
Action: Contact Oracle Support Services.
Cause: Materialized view log on the indicated table already has ROWID information.
Action: No action required.
Cause: The specified ROWID materialized view did not have the required index on the ROWID column of its underlying table.
Action: Drop and recreate the materialized view.
Cause: Materialized view log on the indicated table does not have primary key information.
Action: Add primary keys to the materialized view log using the ALTER MATERIALIZED VIEW command.
Cause: Materialized view log on the indicated table already has primary key columns.
Action: No action required.
Cause: One or more of the specified filter columns did not exist or was a primary key column or a primary key based object identifier.
Action: Ensure that all specified filter columns exist in the master table and ensure that primary key columns or primary key based object identifiers are not included in the list of filter columns.
Cause: One or more of the specified filter columns was already being recorded in the materialized view log.
Action: Describe the materialized view log table and reissue the SQL command with the filter columns that are already being recorded in the materialized view log.
Cause: Pre-Oracle8 master sites are not able to support primary key or subquery materialized views that are able to perform a fast refresh.
Action: Create a ROWID materialized view or use a master table from an Oracle8 site.
Cause: An attempt was made to use LOB columns as filter columns.
Action: Remove LOB columns from the filter columns list and retry command.
Cause: The materialized view log did not exist or did not log the information needed by the materialized view to perform a fast refresh.
Action: Ensure that the materialized view log exists and logs the necessary information.
Cause: The materialized view log either did not have primary key columns logged, or the timestamp associated with the primary key columns was more recent than the last refresh time.
Action: A complete refresh is required before the next fast refresh. Add primary key columns to the materialized view log, if required.
Cause: The materialized view log either does not have ROWID columns logged, or the timestamp associated with the ROWID columns is more recent than the last refresh time.
Action: A complete refresh is required before the next fast refresh. Add ROWID columns to the materialized view log, if required.
Cause: The materialized view log either did not have filter columns logged, or the timestamp associated with the filter columns was more recent than the last refresh time.
Action: A complete refresh is required before the next fast refresh. Add filter columns to the materialized view log, if required.
Cause: The materialized view log was younger than the last refresh.
Action: A complete refresh is required before the next fast refresh.
Cause: The materialized view log did not exist or could not be used.
Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log, REFRESH FAST will be available starting the next time the materialized view is refreshed.
Cause: The updatable materialized view log was not empty. The updatable materialized view log must be empty before an updatable rowid materialized view can be altered to a primary key materialized view.
Action: Ensure that updatable materialized view log is empty by refreshing the materialized view before converting the updatable ROWID materialized view to a primary key materialized view.
Cause: An attempt was made to import a materialized view exported by an unknown export version (for example, from a newer release than the importing site).
Action: Re-export the file using a version of export known by the importing site.
Cause: A local rollback segment was specified in the CREATE MATERIALIZED VIEW command, but automatic refresh parameters were not specified. Therefore a refresh group was not created to automatically refresh the materialized view and the local rollback segment can't be registered for future use.
Action: Either supply the automatic refresh parameters so that a refresh group will be created or do not specify a local rollback segment.
Cause: An attempt was made to specify master rollback segment in the current operation. The master site of the current materialized view does not allow users to specify a rollback segment to be used for materialized view operations. This feature is only supported by Oracle8 or later master sites.
Action: Do not specify a master rollback segment in the current operation or choose a new master site.
Cause: Index-organized tables do not have ROWIDs. Therefore a materialized view log that records the ROWIDs of an index-organized table could not be created.
Action: Do not include the WITH ROWID option when using the CREATE MATERIALIZED VIEW command and do not include the ADD ROWID option when using the ALTER MATERIALIZED VIEW command if the master table is index-organized.
Cause: An attempt was made to alter job_queue_processes in single process mode.
Action: Do not attempt to set job_queue_processes in single process mode.
Cause: An invalid option was used in a CREATE MATERIALIZED VIEW statement.
Action: Specify only valid options.
Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG statement.
Action: Specify only valid options.
Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG statement.
Action: Specify only valid options.
Cause: The ON COMMIT refresh attribute, incompatible with other refresh options such as automatic periodic refresh, was specified.
Action: Specify only valid options.
Cause: Either ROWIDs of certain tables were missing in the definition or the inner table of an outer join did not have UNIQUE constraints on join columns.
Action: Specify the FORCE or COMPLETE option. If this error occurred during creation, the materialized view definition may have been changed. Refer to the documentation on materialized views.
Cause: The list of objects in the FROM clause of the definition of this materialized view had some dependencies upon each other.
Action: Refer to the documentation to see which types of nesting are valid.
Cause: The materialized view did not satisfy conditions for refresh at commit time.
Action: Specify only valid options.
Cause: The materialized view query definition introduced a cyclic dependency with existing materialized views.
Action: Modify the materialized view query definition.
Cause: The NEVER REFRESH option may not be used under the following conditions:
Action: For updatable materialized views, reissue the SQL command using REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only materialized views, reissue the SQL command using ON DEMAND.
Cause: The status of the materialized view was INVALID and an attempt was made to fast refresh the materialized view.
Action: Perform a complete refresh of the materialized view. Check the value of the STATUS column in dba_mviews, all_mviews, or user_mviews to verify that the materialized view is VALID after the complete refresh.
Cause: An attempt was made to use the prebuilt tables.
Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED.
Cause: The specified prebuilt table did not exist.
Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table exists.
Cause: The number of columns or the type or the length semantics of a column in the prebuilt table did not match the materialized view definition query.
Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table matches the materialized view definition query.
Cause: An invalid option was used in an ALTER MATERIALIZED VIEW statement.
Action: Specify only valid options.
Cause: A transaction from the client site was received out of sequence. This implies that one or more transactions were missing.
Action: Ensure that the transaction queue at the client site is valid and has not been corrupted.
Cause: The current transaction from the client site could not be applied to the master site.
Action: Ensure that the client site is still valid and that it has not been dropped from the master site.
Cause: The client site was attempting to perform a refresh with an invalid refresh sequence.
Action: Perform a complete refresh to synchronize the refresh sequence number.
Cause: The specified refresh group did not exist at the master site.
Action: Ensure that the client site is still valid and that it has not been dropped from the master site.
Cause: The Replication API does not support the following options and types of materialized view:
Action: Create a PRIMARY KEY materialized view using REFRESH WITH PRIMARY KEY and/or remove the invalid options.
Cause: The refresh group being instantiated did not contain any materialized views.
Action: Modify the template to include at least one materialized view.
Cause: The updatable materialized view was missing the updatable materialized view log required to track updates made to the materialized view.
Action: Create the updatable materialized view log.
Cause: Only materialized views can be offline instantiated. The object being offline instantiated was not a valid materialized view.
Action: Remove the object from the template or replace the object with a valid materialized view.
Cause: Offline instantiation does not support materialized views using the following options:
Action: Remove the invalid options.
Cause: Offline instantiation requires materialized view definition queries to observe the following constraints:
Action: Modify the materialized view definition query.
Cause: The updatable materialized view is missing the updatable materialized view log that is required to track updates made to the materialized view.
Action: Create the updatable materialized view log.
Cause: An out-of-sequence request was made and it cannot be processed.
Action: Try again with a valid request.
Cause: An attempt was made to access an invalid memory region.
Action: Reconnect and try the command again.
Cause: ] An attempt was made to access an invalid field or object in the Java Virtual Memory.
Action: Retry the request.
Cause: The result set threshold or LOB threshold value is not supported.
Action: Specify a threshold value below 64K.
Cause: Temporary updatable materialized view log was not created or was dropped.
Action: Re-create the temporary updatable materialized view log.
Warning: This will cause a complete refresh of the materialized view.
Cause: Refresh result set sent through client method REFRESH_REQ_RESULT returned an unknown value.
Action: Re-issue the refresh request.
Cause: The following materialized view options require an 8.1 or higher compatibility setting:
The following materialized view options require a 9.0.0 or higher compatibility setting:
Action: Shut down and restart with an appropriate compatibility setting.
Cause: An attempt was made to update a read-only materialized view. Only Oracle is allowed to update a read-only materialized view.
Action: No action required.
Cause: An attempt was made to create an index-organized materialized aggregate view or an index-organized updatable ROWID materialized view. This is not supported.
Action: Try to create the materialized view without the index organization clause.
Cause: An attempt was made to drop a materialized view using a command other than DROP MATERIALIZED VIEW.
Action: Use the DROP MATERIALIZED VIEW command.
Cause: An attempt was made to alter a materialized view using a command other than ALTER MATERIALIZED VIEW.
Action: Use the ALTER MATERIALIZED VIEW command.
Cause: Materialized view log on the indicated table already has object id information.
Action: No action required.
Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the WITH OBJECT ID option and the master table is not an object table.
Action: Either specify the name of an object table, or remove the WITH OBJECT ID clause.
Cause: An attempt was made to online redefine a table owned by SYS or SYSTEM.
Action: Do not attempt to online redefine a table owned by SYS or SYSTEM.
Cause: An attempt was made to online redefine a table containing a LONG column, an ADT column, or a FILE column.
Action: Do not attempt to online redefine a table containing a LONG column, an ADT column, or a FILE column.
Cause: An attempt was made to online redefine a table that does not have a primary key defined on it.
Action: Do not attempt to online redefine a table that does not have a primary key defined on it.
Cause: An attempt was made to online redefine a table that is either a clustered table, AQ table, temporary table, or IOT overflow table.
Action: Do not attempt to online redefine a table that is a clustered table, AQ table, temporary table, or IOT overflow table.
Cause: An attempt was made to online redefine a table that had materialized views defined on it or had a materialized view log defined on it or is a master.
Action: Drop all materialized views and materialized view logs before attempting to online redefine the table.
Cause: An attempt was made to online redefine a table that is either a materialized view or a replicated table.
Action: Do not attempt to online redefine a table that is either a materialized view or a replicated table.
Cause: The table is not the interim table of the corresponding table to be online redefined.
Action: Pass in the valid interim table.
Cause: There was an error during the online redefinition process.
Action: Abort the online redefinition process.
Cause: There was an error originating from this materialized view log. One possible cause is that schema redefinition has occurred on the master table and one or more columns in the log is now a different type than the corresponding master columns. Another possible cause is that there is a problem accessing the underlying materialized view log table.
Action: Check further error messages in the stack for more detail about the cause. If there has been schema redefinition, drop the materialized view log and recreate it.
Cause: There are some changes (that is, conventional DML, direct load, partition maintenance operation) in the master tables during materialized view refresh.
Action: Refresh the affected materialized views again.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
