45 QSM-00501 to QSM-03287

QSM-00501: unable to initialize Summary Advisor environment
Cause: The Summary Advisor external procedure initialization process failed.
Action: Contact Oracle Worldwide Support.
QSM-00502: OCI error
Cause: A OCI callback routine reported an error
Action: Contact Oracle Worldwide Support.
QSM-00503: out of memory
Cause: Summary Advisor failed to allocate the necessary memory.
Action: Contact Oracle Worldwide Support.
QSM-00504: internal error
Cause: An internal error occurred.
Action: Contact Oracle Worldwide Support.
QSM-00505: syntax error
Cause: A syntax error occurred.
Action: Correct syntax error if possible or contact Oracle Worldwide Support.
QSM-00506: no fact-tables could be found
Cause: The fact-filter is not specified, and there are no fact-tables in the warehouse. A fact-table is a table having foreign-key constraints to one or more of the dimension-tables in the data warehouse.
Action: Check the fact-filter is correctly specified; check that appropriate constraints exist; and the user has privileges to access the tables
QSM-00507: no dimensions could be found
Cause: The database does not have any dimensions
Action: Create the dimensions in your warehouse
QSM-00508: statistics missing on tables/columns
Cause: The system metadata does not contain statistics on one or more tables or columns. The Advisor needs cardinalities of all fact-tables, and of the level-keys of all dimensions in the data warehouse.
Action: Run ANALYZE on the tables and summaries in the warehouse to collect statistics
QSM-00509: invalid parameter
Cause: The indicated parameter has an invalid value
Action: Supply a value in the proper range
QSM-00510: statistics missing on materialized views
Cause: The system metadata does not contain statistics on one or more materialized views. The Advisor needs cardinalities of all materialized views in the data warehouse.
Action: Run ANALYZE on the tables and materialized views in the warehouse to collect statistics.
QSM-00511: invalid fact-tables specified in fact-filter
Cause: The tables specified in the fact-filter are not valid fact-tables. A fact-table must have foreign-key constraints to one or more of the dimension-tables in the data warehouse.
Action: Check the fact-filter is correctly specified; check that appropriate constraints exist; and the user has privileges to access the tables
QSM-00512: invalid summaries specified in the retention-list
Cause: The summaries specified in the retention-list are not valid.
Action: Check the spelling of the summary-names; check that they are valid; and the user has privileges to access them.
QSM-00513: one or more of the workload tables is missing
Cause: One or both of the workload tables are missing. The two workload tables which should be present in the user's schema are V_192216243_F_5_E_14_8_1 and V_192216243_F_5_E_15_8_1; the former is mapped to WORK$_IDEAL_MVIEW and the latter to WORK$_MVIEW_USAGE. The workload tables are created by the Oracle Trace Formatter when the data-collection-file (oraclesm.dat) is formatted by the user.
Action: Check whether the Formatter succeeded in formatting the data collection. Sometimes the V_192216243_F_5_E_14_8_1 (i.e WORK$_IDEAL_MVIEW) may not be created whereas the other table is created. The most likely cause of this is the init.ora parameters needed to invoke mview-rewrite are not enabled. Check your documentation for all the init.ora parameters which need to be set for mview-rewrite to occur. Another possibility is no GROUP BY queries were issued during the time the data was collected, in which case, run the Trace collection for a longer time to get a representative sampling of the queries issued in the data warehouse.
QSM-00514: the size of must-retain summaries exceeds specified space limit
Cause: The specified space limit is greater than the size of must-retain summaries.
Action: Reduce the number of must-retain summaries or increase the space limit
QSM-00515: operation cancelled by user
Cause: The operation has been cancelled by the user
Action: None
QSM-00516: illegal status detected for run
Cause: The run has encountered an illegal value in the status field of the mview$_adv_log table. This could be internal error or an application error.
Action: Contact Oracle Worldwide Support.
QSM-00517: Summary Advisor requires a COMPATIBLE setting of 8.1.0.0 or greater
Cause: The current database has a compatibility setting that is earlier than the supported server version.
Action: Adjust the instance parameter COMPATIBLE to 8.1.0.0 or greater.
QSM-00518: Java is not enabled. Please execute INITJVM.SQL and INITQSMA.SQL
Cause: The current database has has not be created or upgraded to support Java stored procedures. Summary Advisor requires Java stored procedures.
Action: Log into the database with SYSDBA privileges. Execute the INITJVM.SQL script which is found in the ORACLE home directory under JAVAVM. Next, execute the INITQSMA.SQL script found in the ADMIN directory under the ORACLE home.
QSM-00519: Summary Advisor is not installed. Please execute INITQSMA.SQL.
Cause: The current database has has not be created or upgraded to support Summary Advisor. Summary Advisor requires several Java stored procedures.
Action: Log into the database with SYSDBA privileges. Execute the INITQSMA.SQL script found in the ADMIN directory under the ORACLE home. **** **** Messages 520-700 are in the 9i Summary Advisor Java modules 701-708 are Hypothetical Workload generator journal messages
QSM-00710: data access error in module string
Cause: SQL Access Advisor detected a severe error while accessing the advisor repository.
Action: See the accompanying error message for approprate actions.
QSM-00750: the specified value string for parameter string is invalid or contains an invalid item
Cause: The user attempted to set a task parameter using invalid data.
Action: Adjust the data value and retry the operation.
QSM-00751: the file string could not be opened for write access
Cause: Access Advisor could not create the script or report due to a file system error.
Action: Verify the location for file write access and retry the operation.
QSM-00752: the parameter string contains an invalid combination of options string
Cause: The user specified correct option keywords, but entered a combination that is not supported within Access Advisor.
Action: Validate the correct option usage and retry the operation.
QSM-00753: the specified value string is out of the acceptable range of string to string for parameter string
Cause: The user attempted to set a task parameter using invalid data.
Action: Adjust the data value and retry the operation.
QSM-00754: task string does not reference a valid workload and therefore cannot be executed
Cause: The user attempted to execute a advisor task that requires a workload.
Action: Specify a workload for the task and retry the operation.
QSM-00755: a set of workload statements already exists for workload string
Cause: The user attempted to save workload data into an existing workload that already contains data without specifying APPEND or REPLACE.
Action: Validate the import mode retry the operation.
QSM-00756: the specified workload string is being used by one or more advisor tasks
Cause: The user attempted to modify or delete a workload that is currently being used by another task.
Action: Remove the workload reference from the advisor task and retry the operation.
QSM-00757: the specified workload string is not referenced by task string
Cause: The user attempted to delete invalid workload reference from the task.
Action: Validate the workload reference and retry the operation.
QSM-00758: the specified parameter string is not valid for workload string
Cause: The user attempted to access a workload parameter that is does not exist for the specified workload. The parameter may be misspelled or the user selected a parameter that is not supported by the particular advisor.
Action: Validate the parameter name and retry the operation.
QSM-00759: the user string does not exist for the specified workload statement
Cause: The user attempted to add a new SQL statement with an invalid username.
Action: Adjust the name and retry the operation.
QSM-00760: the import mode string is invalid for the current operation
Cause: The user attempted to store data in the repository with an invalid import mode.
Action: Use one of the following valid values: NEW, APPEND, or REPLACE.
QSM-00761: the priority string is invalid for the current operation
Cause: The user attempted to store data in the repository with an invalid priority.
Action: Use one of the following valid values: 1, 2, 3.
QSM-00762: the specified Summary Advisor workload string does not exist
Cause: The user attempted to import an advisor workload from an invalid or non-existent Summary Advisor workload.
Action: Validate the Summary Advisor workload identifier and retry the operation.
QSM-00763: the owner string was not found while validating user-defined workload string.string
Cause: The user attempted to import an advisor workload from a user who may not access to the table.
Action: Validate the location of the user-defined workload.
QSM-00764: the column string was not found in the user-defined workload table string.string
Cause: The user attempted to import an advisor workload from a user table that does not contain the required column.
Action: Validate the user-defined workload table and retry the operation.
QSM-00765: cannot validate user-defined workload because table string.string is invalid.
Cause: The user attempted to import an advisor workload from a table that is not accessible.
Action: Validate the location of the user-defined workload.
QSM-00766: a SQL statement is required for the current workload operation
Cause: The user attempted to create an entry in a workload collection without specifying a SQL statement.
Action: Validate the SQL statement and retry the operation.
QSM-00767: a SQL cache is not available to user string
Cause: The user attempted to collect a workload from the SQL without having authorization.
Action: Validate the user account and retry the operation.
QSM-00768: the search condition is invalid for the requested operation
Cause: The user provided a invalid SEARCH argument to an Access Advisor workload operation. A search condition must be a valid SQL search condition using only the column names specified in the procedure documentation.
Action: Correct the search condition and retry the operation.
QSM-00769: the SQL statement string was not found for workload string
Cause: The user attempted to access a SQL statement that does not exist in the workload.
Action: Validate the SQL statement identifier and retry the operation.
QSM-00770: the specified workload string is already referenced by task string
Cause: The user attempted to add a workload reference to a task when the task already contains the reference.
Action: Validate the workload reference and retry the operation.
QSM-00771: the specified SQL statement cannot be stored in the workload because it has no valid table references
Cause: The user attempted to add a workload statement that contains table references that are either system-specified or user-specified invalid tables.
Action: Validate the workload statement and retry the operation.
QSM-00772: the specified SQL statement cannot be stored in the workload due to a statement error
Cause: The user attempted to add a workload statement that contains invalid SQL syntax or an invalid column reference.
Action: Validate the workload statement and retry the operation.
QSM-00773: the parameter string contains the invalid string name string
Cause: The task or workload parameter contains a name that is either too long or does not exist in the database.
Action: Validate the parameter value and retry the operation.
QSM-00774: there are no SQL statements to process for task string
Cause: While executing, the specified task found no valid SQL statements to analyze. Possible causes are: an empty workload, table filtering, or username filtering.
Action: Validate the workload and the appropriate task parameters and retry the operation.
QSM-00775: the specified SQL statement cannot be stored in the workload due to invalid table references
Cause: The user attempted to add a workload statement that contains one or more invalid identifier for the parsing user.
Action: Validate the workload statement and retry the operation.
QSM-00776: the user-defined workload string is missing the following column: string
Cause: The user attempted to import a workload from an external table; however, the table does not contain all of the required columns.
Action: Adjust the target workload table and retry the operation.
QSM-00777: the specified directive string is unsupported at this time
Cause: The user attempted to create a directive that is not currently supported.
Action: Check the advisor documentation for valid directives.
QSM-00778: the specified output filename string is invalid or cannot be accessed
Cause: The user attempted to create a report or script in a file that cannot be written or created.
Action: Adjust the file name or directory and retry the operation.
QSM-00779: the specified directive conflicts with the existing directive string
Cause: The user attempted to add a directive that cannot operate with an existing directive.
Action: Check the advisor documentation for valid directives.
QSM-00780: the task string could not be executed because the workload string is being modified
Cause: While attempting to execute a task, Access Advisor checks for exclusive access to all of the referenced workloads. If any cannot be reserved, then the execution fails.
Action: Wait until the referenced workloads are free for exclusive access retry the operation.
QSM-00781: the specified value string is invalid for parameter string. Valid keywords are string
Cause: The user attempted to set a task parameter using invalid data.
Action: Adjust the data value and retry the operation
QSM-00782: the specified value string is an invalid date format for parameter string
Cause: The user attempted to set a task parameter using invalid date formatting directives.
Action: See the Oracle documentation for valid date-formatting and retry the operation.
QSM-00783: the specified value string contains an invalid date for parameter string
Cause: The user attempted to set a task parameter using invalid date formatting.
Action: A date literal must be in the form DD/MM/YYYY HH24:MI:SS.
QSM-00784: the string string referenced in the list string is invalid for parameter string
Cause: The user attempted to set a task parameter using an invalid username or table specification.
Action: Validate the object name and retry the operation.
QSM-00785: the directive string is not supported for task string at this time
Cause: The user attempted to add an invalid directive to the current task.
Action: Validate the directive and retry the operation.
QSM-00786: the name string is invalid for directive string
Cause: The user attempted to add a directive that contains an empty or invalid object name.
Action: Correct the name and retry the operation.
QSM-00787: the tablespace string is invalid for directive string
Cause: The user attempted to add a directive that contains an empty or invalid tablespace name.
Action: Correct the name and retry the operation.
QSM-00788: The requested recommendation does not support direct implementation
Cause: The user attempted to use the DBMS_ADVISOR.IMPLEMENT_TASK procedure to implement a SQL Access Advisor recommendation that cannot be implemented due to its complexity.
Action: The user must generate a script and implement the recommendation outside of the SQL Access Advisor.
QSM-00789: The requested recommendation requires user editing and cannot be implemented
Cause: The user attempted to use the DBMS_ADVISOR.IMPLEMENT_TASK procedure to implement a SQL Access Advisor recommendation that cannot be implemented because it requires additional scripting information from the user.
Action: The user must generate a script and edit the results.
QSM-00790: the workload string cannot be modified or changed because it is being used by task string
Cause: The user attempted to change or delete a workload that is referenced by an active task.
Action: Remove references to a workload from any tasks that reference that workload, unless the task is in its initial task state.
QSM-00791: the specified SQL statement cannot be stored in the workload because is contains unsupported statement type
Cause: The user attempted to add a workload statement that contains an invalid statement type. Supported statement types are INSERT, DELETE, UPDATE, SELECT and MERGE.
Action: Validate the workload statement and retry the operation.
QSM-00792: the specified SQL statement cannot be stored in the workload because one or more tables have missing statistics
Cause: The user attempted to add a workload statement that contains a table without statistics. Access Advisor requires all referenced tables to have valid statistics.
Action: Validate the workload statement and retry the operation.
QSM-00793: the specified SQL Tuning Set string does not exist
Cause: The user specified a SQL Tuning Set that has not been defined in the SQL Tuning Set repository.
Action: Correct the SQL Tuning Set name and retry the operation.
QSM-00794: the statement can not be stored due to a violation of the string filter
Cause: The user attempted to manually add a workload statement that failed a filter test. Manual statements must meet the same filtering guidelines as imported statements.
Action: Adjust the attributes or the filter and retry the operation.
QSM-00795: the SQL Tuning Set repository has not been implemented
Cause: The user attempted to collect a workload from a SQL Tuning Set repository that has not yet been implemented or enabled.
Action: Validate the existence of the repository and retry the operation.
QSM-00796: the specified SQL statement cannot be stored in the workload because table string does not have valid statistics
Cause: The user attempted to add a workload statement that references a table with missing statistics.
Action: Gather statistics for the referenced table and retry the operation.
QSM-00797: the specified workload string does not exist for the current user
Cause: The user attempted to reference an Access Advisor workload using a name that does not exist in the Advisor repository.
Action: Adjust the name and retry the operation.
QSM-00798: the specified workload string already exists
Cause: The user attempted to create the specified workload using a name that already exists in the Advisor repository. Task names must be unique to the database user.
Action: Adjust the name and retry the operation.
QSM-00799: the user-defined workload table string cannot be found
Cause: The user has attempted to import a workload from an external table that does not exist or cannot be accessed.
Action: Adjust the target workload table and retry the operation.
QSM-00800: the specified workload name string is invalid
Cause: The user has specified an invalid workload name.
Action: Adjust the target workload name and retry the operation.
QSM-00801: the specified username string is invalid
Cause: The user has specified an invalid username.
Action: Adjust the target username and retry the operation.
QSM-00802: An error occurred while implementing action string (string) string.
Cause: While performing IMPLEMENT_TASK, a specific action operation failed.
Action: Make the necessary adjustments as specified in the secondary message and retry the operation.
QSM-00803: The STORAGE_CHANGE parameter value string cannot be zero or negative for partial workloads.
Cause: While performing EXECUTE_TASK, the user specified a STORAGE_CHANGE value that is incompatible with the type of workload data.
Action: Set a positive STORAGE_CHANGE value.
QSM-00804: not enough space for mandatory access structures
Cause: While performing EXECUTE_TASK, the user specified a STORAGE_CHANGE value that leaves no space for mandatory access structures, such as primary key indexes.
Action: Set a greater STROAGE_CHANGE value.
QSM-00805: the specified recommendation string value string is invalid
Cause: The user has specified an invalid value when attempting to change a recommendation attribute.
Action: Adjust the target attribute value and retry the operation.
QSM-00806: the string parameter value must be specified when STORAGE_MODE is set to TOTAL
Cause: While performing EXECUTE_TASK, the user specified a STORAGE_MODE of TOTAL, but failed to set the DEF_MVIEW_OWNER and DEF_INDEX_OWNER to valid owner names.
Action: Set the specified owner to a valid name
QSM-00807: the ANALYSIS_SCOPE parameter value contains an incomplete or invalid combination of options.
Cause: Though the ANALYSIS_SCOPE parameter supports several options, some combination are not supported.
Action: Enter a valid combination of options.
QSM-00808: parameter string only permits a single keyword. Choose one of the following: string
Cause: The user attempted to set a task parameter using multiple keywords.
Action: Adjust the data value and retry the operation
QSM-00809: the selected number of recommendations exceeds the maximum value of string
Cause: While executing GET_TASK_SCRIPT, an attempt was made to fetch a script having too many recommendations. The limit has been set in order to avoid possible performance and out-of-memory errors.
Action: Select a small set of recommendations prior to fetching the script
QSM-00999: Advisor feature is not currently implemented
Cause: The user attempted to execute an unsupported advisor operation.
Action: Verify the availability of the operation.
QSM-01001: query rewrite not enabled
Cause: When query rewrite is disabled, no query rewrite will take place.
Action: Enable query rewrite with ALTER SESSION SET QUERY_REWRITE ENABLE command.
QSM-01002: no query rewrite when OPTIMIZER_MODE is rule based
Cause: Query rewrite did not occur because the OPTIMIZER_MODE was set to RULE.
Action: Change the optimizer mode using the OPTIMIZER_MODE parameter.
QSM-01003: no query rewrite on DDL queries
Cause: If query contains any data definition operations, no query rewrite will take place.
Action: None
QSM-01004: no query rewrite before view merging
Cause: Internal session parameter _QUERY_REWRITE_2 is set to FALSE
Action: Change session parameter with ALTER SESSION command.
QSM-01005: no query rewrite when query has slave SQL
Cause: Current prcess is a kxfx slave
Action: None
QSM-01006: query rewrite disabled for this query block
Cause: During query rewrite, certain view query blocks cannot be rewritten.
Action: None
QSM-01007: query has NOREWRITE hint
Cause: When query contains a NOREWRITE hint, no query rewrite will take place for that query block.
Action: Remove the NOREWRITE hint from the query
QSM-01008: no query rewrite for update queries
Cause: If a query or part of it has any DML update operations, no query rewrite will take place.
Action: None
QSM-01009: query rewritten with materialized view, string, using text match algorithm
Cause: The query was rewritten using a materialized view, because query text matched the definition of the materialized view
Action: None
QSM-01010: table(s) in the query not found in materialized view, string
Cause: If the materialized view does not reference the base tables found in the query, it cannot be used for rewrite
Action: None
QSM-01011: when heuristic rewrite not set, rewrite hint required
Cause: When using a stored outline, a rewrite hint is required for query rewrite
Action: None
QSM-01012: SAMPLE clause present in FROM
Cause: If a query contains a SAMPLE clause, query rewrite will not take place
Action: None
QSM-01013: nested aggregates or CONNECT BY/START WITH clause present
Cause: If the query contains nested aggregates, CONNECT BY clause, or START WITH clause, query rewrite will not take place
Action: None
QSM-01014: top level operator in WHERE clause of the query is an OR
Cause: If the top-level operator in the WHERE clause is an OR and there is more than one table in the FROM list, then query rewrite will not take place.
Action: None
QSM-01015: GROUP BY clause has non-columns
Cause: No query rewrite, if there is no valid column in the GROUP BY clause.
Action: None
QSM-01016: Query rewrite does not support, aggregate, string
Cause: No query rewrite, if the query contains any DISTINCT aggregates other than COUNT, MIN or MAX.
Action: None
QSM-01017: aggregate argument cannot be converted to canonical form
Cause: Argument of each aggregrate in the query needs to be convertible into a canonical form for query rewrite.
Action: None
QSM-01018: single table materialized join view rewrite not required
Cause: Materialized join view is more expensive for rewrite than using the base table
Action: None
QSM-01019: no suitable materialized view found to rewrite this query
Cause: There doesn't exist any materialized view in the dataware house that can be used to rewrite this query.
Action: Consider creating a new materialized view.
QSM-01020: materialized view, string, is ineligible
Cause: Materialized view is probably disabled or stale.
Action: Consider enabling the materialized view for rewrite or refreshing it.
QSM-01021: materialized view, string, not found in the hint list
Cause: There is a rewrite hint list specified in the query, but this materialized view is not among the hinted ones.
Action: Include this materialized view in the rewrite hint list.
QSM-01022: a more optimal materialized view than string was used to rewrite
Cause: Query Rewrite always chooses the most optimal materialized view based on certain parameters, such as cardinality of the materialized view, number of joins etc. The materialized view specified was found to be less optimal.
Action: To force using a materialized view, consider using a rewrite hint.
QSM-01023: materialized view, string, has GRANT errors
Cause: Materialized view probably has some metadata errors.
Action: Consider recreating it.
QSM-01024: materialized view, string, has unknown compile errors
Cause: Materialized view probably has some metadata errors.
Action: Consider recreating it.
QSM-01025: materialized view, string, not found
Cause: The specified materialized view is not found in the database.
Action: Check the spelling or create a new materialized view
QSM-01026: query rewrite is disabled for, string
Cause: Query rewrite could not use this materialized view, because query rewrite was not enabled for it.
Action: Enable query rewrite for the materialized view with ALTER MATERIALIZED VIEW "mv" ENABLE QUERY REWRITE command, where "mv" is the name of the materializev view.
QSM-01027: materialized view, string, is unusable
Cause: Materialized view probably has some metadata errors.
Action: Consider recreating it.
QSM-01028: materialized view, string, is currently being refreshed
Cause: Materialized view cannot be used for query rewrite while it is being refreshed
Action: Rerun the query, after the refresh operation is completed.
QSM-01029: materialized view, string, is stale in ENFORCED integrity mode
Cause: A stale materialized view cannot be used for query rewrite when the query rewrite integrity mode is set to ENFORCED.
Action: Refresh the materialized view or alter the rewrite integrity mode with ALTER SESSION QUERY_REWRITE_INTEGRITY = STALE TOLERATED command.
QSM-01030: materialized view, string, has PL/SQL functions in ENFORCED integrity mode
Cause: A materialized view with PL/SQL functions in its definition cannot be used for query rewrite when query rewrite integrity is set to ENFORCED.
Action: Consider running the query in STALE TOLERATED mode.
QSM-01031: materialized view, string, is stale in TRUSTED integrity mode
Cause: A stale materialized view cannot be used for query rewrite when the query rewrite integrity mode is set to TRUSTED.
Action: Refresh the materialized view or alter the rewrite integrity mode with ALTER SESSION QUERY_REWRITE_INTEGRITY = STALE TOLERATED command.
QSM-01032: materialized view, string, not found
Cause: There was no associated metadata for the materialized view.
Action: Check the spelling and re-run the query.
QSM-01033: query rewritten with materialized view, string
Cause: The specified materialized view was used to rewrite the given query.
Action: None
QSM-01034: materialized view, string, needs a dimension level to join table, string
Cause: One or more hierarchical relationship(s) in the table(s) could not be established.
Action: Consider adding a level in the dimension to provide the missing intra- table relationships.
QSM-01035: a row level security policy exists on this table
Cause: Any row level security policy that may exist on a base-table prevents exact text match query rewrite.
Action: None
QSM-01036: unmatched column, string, present in query after view merging
Cause: Clearing the columns after view merging failed due to some reasons - bug??
Action: None
QSM-01037: Query Rewrite failed to allocate the necessary query join graph
Cause: Join graph allocation and initialization failed, possibly due to one or more undetermined operand(s) in the query expression.
Action: None
QSM-01038: logical operator(s) could not be processed
Cause: One or more logical operator(s) in the query predicates could not be processed, possibly due to invalid operator(s).
Action: None
QSM-01039: selection present on right hand side of an outer join
Cause: Query cannot be rewritten if any predicate contains a selection on the right hand side of an outer join.
Action: None
QSM-01040: match between the materialized view (string) and query join graphs failed
Cause: Query rewrite will not take place if the joins in the query and the materialized view do not have any match.
Action: None
QSM-01041: materialized view, string, does not match with a measure in the query
Cause: If a measure (such as SUM, AVERAGE) in the query cannot be matched or computed from the materialized view, it will not be used for rewrite.
Action: None
QSM-01042: anchor and matching join arc check failed for string
Cause: If there is a lossy join in the materialized view that doesn't exist in the query, query rewrite will not take place.
Action: None
QSM-01043: join back attempted on a table to the RHS of a semi or anti join for string
Cause: Query Rewrite will not occur if a join back is required to a table that appears to the right hand side of a semi or anti-join.
Action: None
QSM-01044: join back attempted on a view for string
Cause: Query Rewrite will not occur if a join back to a table is required to find any missing columns.
Action: None
QSM-01046: complex join back on correlated columns not allowed (string)
Cause: Query Rewrite will not occur if a join back is required on a column that is referenced by a sub-query.
Action: None
QSM-01047: complex join back on non-MAV rewrite not allowed (string)
Cause: Query Rewrite can occur by means of a complex join back only during a MAV rewrite.
Action: None
QSM-01048: join back level(s) not present (string)
Cause: Query Rewrite requires joining back to a level of a dimension to find a missing information.
Action: Consider creating a dimension.
QSM-01049: semi-join check failed for materialized view, string
Cause: If there is a semi join in the query, then Query Rewrite will create (select distinct <pk-list>, <ref-col> from mjv) where <pk-list> is the list of rowids/pk of all mjv tables that don't correspond to a right side of a semi-join and <ref-col> are their columns. Query Rewrite will not occur if a join from the materialized view cannot match the semi-join from the query.
Action: None
QSM-01050: roll-up check failed for materialized view, string
Cause: A column in the query cannot be computed from the materialized view.
Action: Consider creating a dimension to supply the missing information
QSM-01051: no support for rollup when a window function is present on the column
Cause: No query rewrite if a window function is present on a column that requires a roll-up to compute a measure.
Action: None
QSM-01052: referential integrity constraint on table, string, not VALID in ENFORCED integrity mode
Cause: A join present in the materialized view requires validated primary/foreign key constraints in ENFORCED query rewrite integrity mode.
Action: Validate the constraint or change the integrity mode with ALTER SESSION SET QUERY_REWRITE_INTEGRITY = STALE_TOLERATED command.
QSM-01053: NORELY referential integrity constraint on table, string, in TRUSTED/STALE TOLERATED integrity mode
Cause: A join present in the materialized view requires RELY mode to be set on the primary/foreign key constraints.
Action: Set the RELY mode with ALTER TABLE <table> MODIFY CONSTRAINT <constraint> RELY command. Alternatively validate the constraint with ALTER TABLE <table> VALIDATE CONSTRAINT <constraint>.
QSM-01054: no join match between query and summary, string
Cause: There are no common joins between the query and the the materialized view
Action: None
QSM-01055: Query Rewrite failed to allocate the necessary materialized view join graph
Cause: Join graph allocation and initialization failed, possibly due to one or more undetermined operand(s).
Action: None
QSM-01056: no query rewrite for this DDL expression
Cause: Some SELECT statements which are part of a DDL expression may be eligible for rewrite. These include CREATE AS SELECT and CREATE OUTLINE statements. The given query expression is a DDL expression, which doesn't fall in this category.
Action: None
QSM-01057: no query rewrite for this DML expression
Cause: Current DML is being done using an updatable view, so it is not eligible for rewrite.
Action: None
QSM-01058: MV, string, does not have column, string, for a joinback
Cause: A GROUP BY column in the query is not present in the GROUP BY clause of of the materialized view. This usually requires a join back to a third table.
Action: None
QSM-01059: HAVING clause in the query block is malformed
Cause: An illegal HAVING clause has been specified in the query.
Action: Correct the query syntax and run the query again.
QSM-01060: illegal subquery in the HAVING clause
Cause: When a HAVING clause has a subquery, then any references to the tables in the outer query should only reference the tables in the GROUP BY clause.
Action: Correct error in the syntax and rerun the query.
QSM-01061: illegal query expression
Cause: An illegal query was specified. Specifically one of the following criteria was not satisfied: (a) All (non-constant, non-aggregate) SELECT expressions in the query should be made up of group expressions. (b) All column references in the HAVING clause should come from the GROUP BY expressions. (c) If there is an ORDER BY clause, then all column references should come from the GROUP BY or SELECT clause, depending on whether the query selects DISTINCT.
Action: Correct error in the syntax and rerun the query.
QSM-01062: query has one or more manual partition(s)
Cause: Query rewrite is not possible if query has any manual partitions.
Action: None
QSM-01063: query has a dictionary table or view
Cause: Query rewrite is not allowed if query references any dictionary tables/views.
Action: None
QSM-01064: query has a fixed table or view
Cause: Query rewrite is not allowed if query references any fixed tables/views
Action: None
QSM-01065: materialized view, string, cannot compute measure, string, in the query
Cause: If the materialized view cannot compute a measure in the query using the measures in its definition, then query rewrite will not occur.
Action: None
QSM-01066: materialized view, string, does not have the column, string, from query
Cause: Query rewrite will not occur, if the materialized view cannot provide all the columns that the query has
Action: None
QSM-01067: materialized view, string, cannot support the query measure, string
Cause: An attempt was made to push a grouping function through an expression specified in the query to transform a measure. Query rewrite will not occur if this measure transformation failed.
Action: None
QSM-01068: no dimensions present
Cause: An attempt was made to load a dimension from the dataware house, but there were no dimensions present.
Action: None
QSM-01069: summary join graph for, string, does not have table, string
Cause: An attempt to locate an object that is part of a join failed.
Action: None
QSM-01070: equivalence class manager was not found
Cause: An equivalence class manager is required to compute the transitive closure for the columns in an equivalence class.
Action: None
QSM-01071: query rewrite not possible because a join in materialized view % with table % has eliminated some rows found in query
Cause: All lossy joins in the materialized view must be present in the query for query rewrite to occur.
Action: None
QSM-01072: materialized view, string, and query have different joins between tables, string
Cause: Anchors, if any, in the MV and query match. But the joins between these anchors in the MV and query are different.
Action: None
QSM-01073: query rewrite not possible because materialized view, string, has a join not found in query
Cause: Query rewrite may not be possible if the materialized view has some joins that query does not have
Action: None
QSM-01074: query rewrite not possible because materialized view, string, and query have different number of joins between tables, string
Cause: Query rewrite may not be possible if the query has some joins that the materialized view does not have between the same pair of tables.
Action: None
QSM-01075: materialized view, string, does not support aggregate function, string
Cause: The specified aggregate function is not found in the materialized view.
Action: None
QSM-01076: no materialized join view was found
Cause: To support an MJV rewrite, we require a materialized join view.
Action: None
QSM-01077: materialized view, string, is grouping at a higher level than query
Cause: If a query column, which is not present in the materialized view, can be obtained by a rollup within the materialized view, then it should group at a higher level than the materialized view.
Action: None
QSM-01078: materialized view, string, is marked invalid
Cause: The materialized view's kglobsta field has KGLSINV bit set.
Action: none ??
QSM-01079: DML operation occurred on a table referenced by MV, string
Cause: If any dependent tables of a materialized view undergoes a DML operation, query rewrite may be restricted depending on the query rewrite integrity mode for the session. In this situation, query rewrite will take place only if the rewrite integrity mode is STALE_TOLERATED.
Action: Consider refreshing the materialized view chaning the rewrite integrity mode to STALE_TOLERATED.
QSM-01080: invalid dimension, string
Cause: This dimension table has authorization or compilation problems.
Action: None
QSM-01081: no primary key or row id found for table, string, in MV, string
Cause: In order to obtain a missing column, the materialized view needs to join back to the above table. But it lacks the primary key or rowid for the table.
Action: None
QSM-01082: Joining materialized view, string, with table, string, not possible
Cause: A column in the query is not found in the summary. To obtain the column, a join back of materialized view to the table by means of either the primary key, foreign key or rowid of the table is required. The specified materialized view does not have the primary key, foreign key or rowid of the table to perform the join operation.
Action: Consider building a dimension-table to provide the missing information.
QSM-01083: query text not available - possible inline view
Cause: During the query rewrite transformation, orignal query was possibly transformed into an inline view.
Action: None
QSM-01084: materialized view string has an anchor table string not found in query
Cause: A table in a materialized view is an anchor, (a) if it is not joined to any other table or (b) joined to other tables but each of its joins is either lossy or lossless with the above table being child-side table. If an anchor which is present in the materialized view is not found in the query, then query rewrite will not take place.
Action: None
QSM-01085: materialized view, string, has a lossy join between tables, string
Cause: There are no primary key, foreign key constraints between these tables. But query rewrite is still possible if the lossy join between the above tables also appear in the query
Action: None
QSM-01086: dimension(s) not present or not used in ENFORCED integrity mode
Cause: Query rewrite does not use dimensions in ENFORCED query rewrite integrity mode. If a suitable dimension is present, consider chaning the current integrity mode to either TRUSTED or STALE_ TOLERATED by using ALTER SESSION SET QUERY_REWRITE_INTEGRITY = command.
Action: None
QSM-01087: query grouping on a column that cannot be derived from materialized view, string
Cause: Query is grouping on undetermined columns.
Action: None
QSM-01089: an inline view in the query does not have a materialized view
Cause: General query rewrite is not possible if an inline view in the query does not have a matching materialized view in the meta data.
Action: None
QSM-01090: no query rewrite after view merging
Cause: Internal session parameter _QUERY_REWRITE_1 is set to FALSE
Action: Change session parameter with ALTER SESSION command.
QSM-01091: cost based optimizer found query rewrite is more expensive
Cause: When cost based optimizer is ON, cost of the rewritten cursor is compared to the cursor generated without query rewrite, and the cheaper one is chosen for execution.
Action: None
QSM-01092: mjv tries to rewrite a semi-join and primary key or rowid missing
Cause: Materialized join view tries to rewrite a semi-join (IN sub-query) and the primary keys or rowids of left tables of semi-joins are missing from MJV.
Action: None
QSM-01093: anti-join marker not found in materialized join view
Cause: Materialized join view has outer join while the query inner join. For rewrite to succeed MV must have an anti-join marker like the rowid or primary key of the right tables of outer join
Action: None
QSM-01094: outer-join filter not found in materialized join view
Cause: Materialized join view has outer join while the query inner join. For rewrite to succeed MV must have an anti-join marker like the rowid or primary key of the right tables of outer join
Action: None
QSM-01095: no suitable grouping_id found in MV with grouping sets
Cause: If materialized aggregate view contains grouping sets, then it also must contain the grouping_id() function. This function must contain all columns in the MV GROUP BY.
Action: None
QSM-01096: Materialized view with grouping sets contains duplicates
Cause: Materialized view with grouping sets contains duplicates and no rewrite is supported for it. For example, GROUP BY GROUPING SET ((a), (a)) is not supported for rewrite.
Action: None
QSM-01097: Materialized view with grouping sets has too long key
Cause: Materialized view with grouping sets has more that 64 different keys in its GROUP BY. No rewrite is supported then.
Action: None
QSM-01098: mv string clause more restrictive than query string clause
Cause: The materialized view contains a selection condition in the WHERE or HAVING clause that is more restrictive than the corresponding selection condition in the request query.
Action: Change the selection criteria in the request query to be at least as restrictive as the selection criteria in the materialized view, or drop and recreate the materialized view using less restrictive selection criteria.
QSM-01099: non-tolerated reference to stale portion of mv for table string
Cause: The materialized view is partially stale. It is stale with respect to one or more partitions in one or more of its detail tables. The request query references one or more such detail partitions.
Action: (1) Change the selection criteria of the request to restrict the query to only the fresh portion of the materialized view, or (2) ALTER {SYSTEM|SESSION} QUERY_REWRITE_INTEGRITY = STALE_TOLERATED or (3) refresh the materialized view.
QSM-01100: containment check failed for mv, string
Cause: The materialized view contains a selection condition in the WHERE or HAVING clause that is more restrictive than the corresponding selection condition in the request query.
Action: Change the selection criteria in the request query to be at least as restrictive as the selection criteria in the materialized view, or drop and recreate the materialized view using less restrictive selection criteria.
QSM-01101: rollup(s) took place on mv, string
Cause: If query's GROUP BY has one of the higher levels of columns found in the materialized view, then the lower level columns in the materialized view will be rolled up to compute the desired results.
Action: None
QSM-01102: materialized view, string, requires join back to table, string, on column, string
Cause: A column in the query does not appear in the materialized view. Query rewrite will try to obtain this column from the base table, by doing a join back to that column with the MV.
Action: None
QSM-01103: there is a remote table, string, referenced in the query
Cause: Query rewrite does not support query with remote tables.
Action: None
QSM-01104: query is using flashback
Cause: Query rewrite does not support flashback.
Action: None
QSM-01105: no primary key or row id in MV, string, is found for table, string
Cause: In order to obtain a missing column, the materialized view needs to join back to the above table. But it lacks the primary key or rowid for the table.
Action: None
QSM-01106: materialized view, string, is stale with respect to some partition(s) in the base table(s)
Cause: Query is requesting some data from the MV that are stale with respect to some partitions in the base tables due to some updates.
Action: refresh the stale partitions and rerun the query
QSM-01107: Partition Containment Tracking (PCT) rewrite is not allowed
Cause: Query rewrite is disabled for PCT through a session parameter
Action: None
QSM-01108: maximum number of disjuncts exceeded in the query string
Cause: Query rewrite engine cannot process the query if the number of disjuncts (OR's)in the WHERE clause exceeds the maximum allowed number. The number of disjuncts in the query and the maximum allowed disjuncts are given at the end of the message in the form of (no of disjuncts in query, maximum disjuncts allowed).
Action: None
QSM-01109: while rewriting with MV, string, table, string, migrated to query delta
Cause: There was an unmatched join on the MV, so a table involved in the join was pushed to the query delta to see if the query can be rewritten
Action: None
QSM-01110: query rewrite not possible with materialized view string because it contains a join between tables (string) that is not present in the query and that potentially eliminates rows needed by the query
Cause: All lossy joins in the materialized view must be present in the query for query rewrite to occur.
Action: None
QSM-01111: no partition key or partition marker found in MV, string
Cause: In order to do query rewrite with fresh partitions of an MV, the MV should have a partiton key or partition marker.
Action: None
QSM-01112: WHERE clause of mv, string, is more restrictive than query
Cause: The materialized view contains a selection condition in the WHERE clause that is more restrictive than the corresponding selection condition in the request query.
Action: Change the selection criteria in the request query to be at least as restrictive as the selection criteria in the materialized view, or drop and recreate the materialized view using less restrictive selection criteria.
QSM-01113: HAVING clause of mv, string, is more restrictive than query
Cause: The materialized view contains a selection condition in the HAVING clause that is more restrictive than the corresponding selection condition in the request query.
Action: Change the selection criteria in the request query to be at least as restrictive as the selection criteria in the materialized view, or drop and recreate the materialized view using less restrictive selection criteria.
QSM-01115: rollup took place on a column with a window function
Cause: There was a rollup to aggregate the data on a column with a window function.
Action: None
QSM-01116: window function computability checks failed
Cause: The window function in the query could not be computed from the materialized view.
Action: None
QSM-01120: recursive rewrite not allowed here
Cause: This query was possibly rewritten with an equivalence which doesn't allow further rewrites.
Action: None
QSM-01121: materialized view, string, is TRUSTED in ENFORCED integrity mode
Cause: A stale materialized view created with USING TRUSTED CONSTRAINTS clause cannot be used when the query rewrite integrity mode is set ENFORCED.
Action: Alter materialized view such that it has the ENFORCED CONSTRAINTS ALTER MATERIALIZED VIEW <mv> REFRESH USING ENFORCED CONSTRAINTS
QSM-01123: self-join algorithm could not resolve multiple instances
Cause: The generalized self-join algorithm could not resolve the mutliple instances, likely due to mismatch in joins or measures
Action: Consider using aliases in the query to match with the aliases in the materialized view
QSM-01124: set operator materialized view, string, doesn't have a marker column
Cause: The specified set operator materialized view does not have a marker column.
Action: Add a marker column to the specified materialized view.
QSM-01125: a more optimal set operator materialized view than string was used to rewrite
Cause: Query Rewrite always chooses the most optimal set operator materialized view based on parameters, such as cardinality of the set operator materialized view, number of branches that the set operator materialized view can rewrite etc. The set operator materialized view specified was found to be less optimal.
Action: To force using a set operator materialized view, consider using a rewrite hint.
QSM-01126: query rewritten with set operator materialized view, string
Cause: The specified set operator materialized view was used to rewrite the given query.
Action: None
QSM-01127: query rewritten with materialized view(s), string
Cause: The query was succesfully rewritten with multiple MVs
Action: None
QSM-01128: Multi MV rewrite is disabled
Cause: When multimv query rewrite is disabled, no multimv query rewrite will take place.
Action: Enable multimv query rewrite with ALTER SESSION SET "_MULTIMV_QUERY_REWRITE_ENABLED" = true .
QSM-01129: query has NO_MULTIMV_REWRITE hint
Cause: WHen the query has this hint no multimv rewrite will be tried for this query
Action: Remove hint from query
QSM-01130: Multi MV rewrite not allowed if at least one query block has no MVs
Cause: When only multimv query rewrite is enabled, every query block should have at least one MV in it's from clause
Action: Disable only multimv query rewrite with ALTER SESSION SET "_ONLY_MULTIMV_QUERY_REWRITE_ENABLED" = false .
QSM-01131: query has ONLY_MULTIMV_REWRITE hint
Cause: When the query has this hint no multimv rewrite will be done if the query has a query block with no MVs in the from clause
Action: Remove hint from query
QSM-01132: query has a named array type column
Cause: When the query has a column of named array type, query rewrite cannot be done
Action: None
QSM-01133: query has an ADT column
Cause: When the query has a column of ADT type, query rewrite cannot be done
Action: None
QSM-01134: query has a hidden or nested table column
Cause: When the query has a hidden or nested table column, query rewrite cannot be done
Action: None
QSM-01135: query has an LOB column
Cause: When the query has a column stored in LOB, query rewrite cannot be done
Action: None
QSM-01136: query has a nested table column
Cause: When the query has a nested table column, query rewrite cannot be done
Action: None
QSM-01137: dimension level, string, marked as SKIP WHEN NULL
Cause: Join back is not possible on a level marked as SKIP WHEN NULL in a dimension
Action: None
QSM-01138: Query rewrite is not allowed.
Cause: Query rewrite was not allowed during materialized view validation.
Action: None
QSM-01139: query rewrite with stale materialized view, string, requires join back
Cause: Query rewrite was not allowed with a stale materialized view if join back to a base table is required.
Action: None
QSM-01150: query did not rewrite
Cause: See the other messages from explain_rewrite() for explanation"
Action: None
QSM-01168: query rewrite not possible when Fine Grain Auditing is present on a base table
Cause: Query rewrite could not take place because Fine Grain Auditing (FGA) was present on a base table in the query
Action: None
QSM-01169: query rewrite not possible for a CREATE or ALTER VIEW statement
Cause: Query rewrite could not take place because the incoming query was either a CREATE or ALTER VIEW statement
Action: None
QSM-01170: no matching objects found between query and materialized view string
Cause: Matching objects were not found between the query and the materialized view. Materialized view may contain only editioning views.
Action: None
QSM-01202: query rewrite not possible when OPTIMIZER_MODE is set to rule based
Cause: Query rewrite did not occur because the OPTIMIZER_MODE was set to RULE.
Action: Change the optimizer mode using the OPTIMIZER_MODE parameter.
QSM-01203: query rewrite not possible on DDL queries
Cause: If query contains any data definition operations, no query rewrite will take place.
Action: None
QSM-01204: query rewrite not possible before view merging
Cause: Internal session parameter _QUERY_REWRITE_2 is set to FALSE
Action: Change session parameter with ALTER SESSION command.
QSM-01205: query rewrite not possible when query has slave SQL
Cause: Current prcess is a kxfx slave
Action: None
QSM-01207: query rewrite not possible when query has a NOREWRITE hint
Cause: When query contains a NOREWRITE hint, no query rewrite will take place for that query block.
Action: Remove the NOREWRITE hint from the query
QSM-01208: query rewrite not possible for update queries
Cause: If a query or part of it has any DML update operations, no query rewrite will take place.
Action: None
QSM-01209: query rewritten with materialized view, string, using text match algorithm
Cause: The query was rewritten using a materialized view, because query text matched the definition of the materialized view
Action: None
QSM-01210: query rewrite not possible because no common table(s) found between materialized view string and query
Cause: If the materialized view does not reference the base tables found in the query, it cannot be used for rewrite
Action: None
QSM-01211: query rewrite not possible when stored outline does not have a rewrite hint
Cause: When using a stored outline, a rewrite hint is required for query rewrite
Action: None
QSM-01212: query rewrite not possible when SAMPLE clause is present in FROM
Cause: If a query contains a SAMPLE clause, query rewrite will not take place
Action: None
QSM-01213: query rewrite not possible when nested aggregates or CONNECT BY clause or START WITH clause or recursive WITH clause is present
Cause: If the query contains nested aggregates, CONNECT BY clause, or START WITH clause, or recursive with clause, query rewrite will not take place
Action: None
QSM-01214: query rewrite not possible if OR is the top level operator in query WHERE clause
Cause: If the top-level operator in the WHERE clause is an OR and there is more than one table in the FROM list, then query rewrite will not take place.
Action: None
QSM-01215: query rewrite not possible when query GROUP BY clause has non-columns
Cause: No query rewrite, if there is no valid column in the GROUP BY clause.
Action: None
QSM-01218: query rewrite is likely more expensive due to a single table match between materialized view and query
Cause: Materialized join view is more expensive for rewrite than using the base table
Action: None
QSM-01219: no suitable materialized view found to rewrite this query
Cause: There doesn't exist any materialized view in the database that can be used to rewrite this query.
Action: Consider creating a new materialized view.
QSM-01220: materialized view, string, is disabled, stale or unusable
Cause: Materialized view is probably disabled or stale.
Action: Consider enabling the materialized view for rewrite or refreshing it.
QSM-01222: materialized view string is less optimal than string
Cause: Query Rewrite always chooses the most optimal materialized view based on certain parameters, such as cardinality of the materialized view, number of joins etc. The materialized view specified was found to be less optimal.
Action: To force using a materialized view, consider using a rewrite hint.
QSM-01241: query measure cannot be derived from the materialized view string
Cause: If a measure (such as SUM, AVERAGE) in the query cannot be matched or computed from the materialized view, it will not be used for rewrite.
Action: None
QSM-01244: join back could not be done on a view for string
Cause: Query Rewrite will not occur if a join back to a table is required to find any missing columns.
Action: None
QSM-01246: join back on correlated columns not allowed (string)
Cause: Query Rewrite will not occur if a join back is required on a column that is referenced by a sub-query.
Action: None
QSM-01247: join back cannot be done on a materialized view that does not have an aggregate (string)
Cause: Query Rewrite can occur by means of a complex join back only during a MAV rewrite.
Action: None
QSM-01248: materialized view does not have the join back level(s) (string)
Cause: Query Rewrite requires joining back to level of a dimension to find missing information.
Action: Consider creating a dimension.
QSM-01251: query rewrite cannot perform rollup due to the presence of a window function
Cause: No query rewrite if a window function is present on a column that requires a roll-up to compute a measure.
Action: None
QSM-01256: query rewrite not possible for this DDL statement
Cause: Some SELECT statements which are part of a DDL expression may be eligible for rewrite. These include CREATE AS SELECT and CREATE OUTLINE statements. The given query expression is a DDL expression, which doesn't fall in this category.
Action: None
QSM-01257: query rewrite not possible for this DML statement
Cause: Current DML is being done using an updatable view, so it is not eligible for rewrite.
Action: None
QSM-01263: query rewrite not possible when query references a dictionary table or view
Cause: Query rewrite is not allowed if query references any dictionary tables/views.
Action: None
QSM-01271: query rewrite not possible because a join in materialized view string with table string has eliminated some rows found in query
Cause: A join from the materialized view to any table that eliminates some rows should be be present in the query. Otherwise query rewrite will not occur.
Action: None
QSM-01273: query rewrite not possible because materialized view string has a join not found in query
Cause: Query rewrite may not be possible if the materialized view has some joins that query does not have
Action: None
QSM-01274: query rewrite not possible because materialized view string and query have different number of joins between tables string
Cause: Query rewrite may not be possible if the query has some joins that the materialized view does not have between the same pair of tables.
Action: None
QSM-01279: query rewrite not possible because DML operation occurred on a table referenced by materialized view string
Cause: If any dependent tables of a materialized view undergoes a DML operation, query rewrite may be restricted depending on the query rewrite integrity mode for the session. In this situation, query rewrite will take place only if the rewrite integrity mode is STALE_TOLERATED.
Action: Consider refreshing the materialized view changing the rewrite integrity mode to STALE_TOLERATED.
QSM-01281: query rewrite not possible because either a primary key or a row id is required to join table string with MV string
Cause: In order to obtain a missing column, the materialized view needs to join back to the above table. But it lacks the primary key or rowid for the table.
Action: None
QSM-01284: materialized view string has an anchor table string not found in query
Cause: A table in a materialized view is an anchor, (a) if it is not joined to any other table or (b) joined to other tables but each of its joins is not guaranteed to provide all the rows or joined with the above table being child-side table. If an anchor which is present in the materialized view is not found in the query, then query rewrite will not take place.
Action: None
QSM-01293: anti-join marker not found in materialized view with joins
Cause: Materialized view has outer join while the query has inner join. For rewrite to succeed MV must have an anti-join marker like the rowid or primary key of the right tables of outer join
Action: None
QSM-01295: no suitable grouping_id found in materialized view with grouping sets
Cause: If materialized view contains grouping sets, then it also must contain the grouping_id() function. This function must contain all columns in the MV GROUP BY.
Action: None
QSM-01296: query rewrite not possible because materialized view contains duplicate grouping sets
Cause: Materialized view with grouping sets contains duplicates and no rewrite is supported for it. For example, GROUP BY GROUPING SET ((a), (a)) is not supported for rewrite.
Action: None
QSM-01297: query rewrite not possible because materialized view with grouping sets has more than 176 different keys
Cause: Materialized view with grouping sets has more that 176 different keys in its GROUP BY. No rewrite is supported then.
Action: None
QSM-01298: materialized view string clause more restrictive than query string clause
Cause: The materialized view contains a selection condition in the WHERE or HAVING clause that is more restrictive than the corresponding selection condition in the request query.
Action: Change the selection criteria in the request query to be at least as restrictive as the selection criteria in the materialized view, or drop and recreate the materialized view using less restrictive selection criteria.
QSM-01299: query rewrite not possible because materialized view string is partially stale
Cause: The materialized view is partially stale. It is stale with respect to one or more partitions in one or more of its detail tables. The request query references one or more such detail partitions.
Action: (1) Change the selection criteria of the request to restrict the query to only the fresh portion of the materialized view, or (2) ALTER {SYSTEM|SESSION} QUERY_REWRITE_INTEGRITY = STALE_TOLERATED or (3) refresh the materialized view.
QSM-01303: query rewrite not possible because query references a remote table string
Cause: Query rewrite does not support query with remote tables.
Action: None
QSM-01304: query rewrite not possible because query is using flashback
Cause: Query rewrite does not support flashback.
Action: None
QSM-01307: Partition Containment Tracking (PCT) rewrite is not allowed
Cause: Query rewrite is disabled for PCT through a session parameter
Action: None
QSM-01308: number of 'OR's in query exceeded the maximum value string
Cause: Query rewrite engine cannot process the query if the number of disjuncts (OR's)in the WHERE clause exceeds the maximum allowed number. The number of disjuncts in the query and the maximum allowed disjuncts are given at the end of the message in the form of (no of disjuncts in query, maximum disjuncts allowed).
Action: None
QSM-01316: window function could not be computed from materialized view string
Cause: The window function in the query could not be computed from the materialized view.
Action: None
QSM-01321: query rewrite not possible because materialized view string has TRUSTED constraints in ENFORCED integrity mode
Cause: A stale materialized view created with USING TRUSTED CONSTRAINTS clause cannot be used when the query rewrite integrity mode is set ENFORCED.
Action: Alter materialized view such that it has the ENFORCED CONSTRAINTS ALTER MATERIALIZED VIEW <mv> REFRESH USING ENFORCED CONSTRAINTS
QSM-01332: query rewrite not possible because query has a named array type column
Cause: When the query has a column of named array type, query rewrite cannot be done
Action: None
QSM-01333: query rewrite not possible because query has an ADT column
Cause: When the query has a column of ADT type, query rewrite cannot be done
Action: None
QSM-01334: query rewrite not possible because query has a hidden or nested table column
Cause: When the query has a hidden or nested table column, query rewrite cannot be done
Action: None
QSM-01335: query rewrite not possible because query has an LOB column
Cause: When the query has a column stored in LOB, query rewrite cannot be done
Action: None
QSM-01336: the materialized view you specified (string) was not used to rewrite the query
Cause: A materialized view specified by the user in the input was not used to rewrite the query, either because query rewrite failed or another more optimal materialized view was used to rewrite.
Action: None
QSM-01339: rewrite not supported on inline view aggregate
Cause: Query has an inline view with an aggregate. Such inline views cannot be matched to any inline views in materialized views.
Action: None
QSM-01340: no inline view match found between query and materialized view(s)
Cause: Query's inline view does not have a match with any inline views in the materialized view
Action: None
QSM-01341: joins between materialized view string and query inline views are different
Cause: There is a mismatch between the joins in the query and materialized view inline views
Action: None
QSM-01342: query rewrite not possible because query has full outer join
Cause: When query block has a table involved in full outer join, query rewrite cannot be done
Action: None
QSM-01343: general inline view rewrite not possible on remote objects
Cause: The general inline view rewrite could not take place because the query had remote objects
Action: None
QSM-01344: general inline view rewrite not possible on this WHERE clause construct
Cause: The general inline view rewrite was not supported with this WHERE clause construct
Action: None
QSM-01345: general inline view rewrite not possible when inline view has subquery
Cause: The general inline view rewrite could not take place because there were subqueries
Action: None
QSM-01346: general inline view rewrite not possible with nested inline views
Cause: General inline view rewrite cannot take place with nested inline views
Action: None
QSM-01347: a query inline view could not be matched with any materialized view inline view
Cause: No materialized view inline views were found to match with a query inline view
Action: None
QSM-01348: an invalid predicate was found in an inline view
Cause: An inline view in the query contained an invalid WHERE clause predicate
Action: None
QSM-01349: general inline view cannot be supported on this inline view
Cause: Certain inline views are unsupported in general inline view rewrite
Action: None
QSM-01350: query rewrite cannot support this inline view
Cause: Certain inline views are unsupported in general inline view rewrite
Action: None
QSM-01351: query inline view has no matching objects with any materialized view inline views
Cause: There were no matching objects between the query inline view and materialized view inline views
Action: None
QSM-01352: SELECT lists of the query and materialized view inline views do not match
Cause: Query inline view's and materialized view inline view's SELECT list items did not match.
Action: None
QSM-01353: no query rewrite on remote objects unless integrity mode is set to stale_tolerated
Cause: Query rewrite's integrity mode should be set to stale_tolerated for query rewrite to occur on queries with remote objects
Action: Set the session parameter, QUERY_REWRITE_INTEGRITY to stale_tolerated
QSM-01354: query rewrite is disabled for remote objects
Cause: Query rewrite was disabled internally for queries referencing remote objects.
Action: None
QSM-01355: multi-mv rewrite not possible in the presence of remote objects
Cause: Multi-MV rewrite not possible for queries referencing remote objects.
Action: None
QSM-01356: query rewrite against cube-organized materialized views not possible when OLAP option is off
Cause: Query rewrite against cube-organized materialized views was not possible because the OLAP option was off.
Action: None
QSM-01509: equivalence, string, matched query text
Cause: The query was rewritten using an equivalence, because query text matched the source statement for this equivalence.
Action: None
QSM-01522: a more optimal equivlanece than string was used to rewrite
Cause: Query Rewrite always chooses the most optimal equivalence based on certain parameters, such as cardinality of the equivalence, number of joins etc. The equivalence view specified was found to be less optimal.
Action: None
QSM-01526: query rewrite is disabled for equivalence, string
Cause: Query rewrite could not use this equivalence, because this equivalence was created as disabled.
Action: Enable this equivalence using alter_rewrite_equivalence procedure from package, dbms_advanced_rewrite.
QSM-01533: query rewritten with equivalence, string
Cause: The specified equivalence was used to rewrite the given query.
Action: None
QSM-01565: equivalence, string, cannot compute measure, string, in the query
Cause: If a measure in the query cannot be computed using the measures in the equivalence, then query rewrite will not occur.
Action: None
QSM-01567: equivalence, string, cannot support the query measure, string
Cause: An attempt was made to push a grouping function through an expression specified in the query to transform a measure. Query rewrite will not occur if this measure transformation failed.
Action: None
QSM-01572: equivalence, string, and query have different joins between tables, string
Cause: Anchors, if any, in the equivalenceand query match. But the joins between these anchors in the equivalence and query are different.
Action: None
QSM-01582: Joining equivalence, string, with table, string, not possible
Cause: A column in the query is not found in the equivalence. To obtain the column, a join back of equivalence to the table by means of either the primary key, foreign key or rowid of the table is required. But join backs are not allowed for equivalence rewrite
Action: None
QSM-01584: equivalence, string, has anchor, string, not found in query
Cause: If an anchor which is present in the equivalence is not found in the query, then query rewrite will not take place.
Action: None
QSM-01601: rollup(s) took place on equivalence, string
Cause: If query's GROUP BY has one of the higher levels of columns found in the equivalence, then the lower level columns in the equivalence will be rolled up to compute the desired results.
Action: None
QSM-01602: equivalence, string, requires join back to table, string, on column, string
Cause: A column in the query does not appear in the equivalence. Query rewrite will try to obtain this column from the base table, by doing a join back to that column with a materialized view. But join backs are not allowed for equivalence rewrite as the required constraints are not guaranteed to be found on the tables in the destination statement of the equivalence.
Action: None
QSM-01610: a lossy join in equivalence, string, between tables, string, not found in query
Cause: All lossy joins in the equivalence must be present in the query for query rewrite to occur.
Action: None
QSM-01617: equivalence definition is disabled
Cause: There is an equivalence defition that could have been probably used by query rewrite to rewrite the query. But this equivalence is disabled.
Action: None
QSM-01618: equivalence, string, is enabled for text match rewrite only
Cause: This equivalence was created for text match rewrite only
Action: None
QSM-01619: equivalence cannot be used in ENFORCED integrity mode
Cause: An equivalence cannot be used for query rewrite when the query rewrite integrity mode is set to ENFORCED.
Action: None
QSM-01621: join backs to base tables not allowed with an equivalence
Cause: Query rewrite needs to do a join back to a base table column to answer this query. But join back is not allowed for an equivalence rewrite
Action: None
QSM-01709: query rewritten with equivalence, string, using text match algorithm
Cause: The query was rewritten using an equivalence because query text matched the definition of the equivalence
Action: None
QSM-01784: equivalence string has an anchor table string not found in query
Cause: A table in an equivalence is an anchor, if (a) it is not joined to any other table or (b) it is joined to other tables but each of its joins is not guaranteed to provide all the rows or joined with the above table being child-side table. If an anchor which is present in the equivalence is not found in the query, then query rewrite will not take place.
Action: None
QSM-01837: recursive query rewrite on equivalence, string, not permitted
Cause: The source and destination statements of this equivalence MV are possibly identical. A recursive rewrite on this equivalence can lead to an infinite loop and thus not permitted.
Action: None
QSM-01838: semijoin transformation not supported on equivalence
Cause: There was a semijoin transformation attempted on an equivalence rewrite. Currently this is not allowed
Action: None
QSM-02001: clustered mv container table
Cause: The capability in question is not supported on a materialized view that has a clustered container table.
Action: Recreate the materialized view using a conventional container table.
QSM-02002: DISTINCT aggregate measure in SELECT list
Cause: The capability in question is not supported when the materialized view uses the DISTINCT qualifier on an aggregate function.
Action: Remove the DISTINCT qualifier.
QSM-02003: aggregate function nested within an expression
Cause: The capability in question is not supported when the materialized view contains an aggregate function invocation nested within an outer expression.
Action: Re-phrase the expression such that the aggregate function invocation is not nested.
QSM-02004: grouping column omitted from SELECT list
Cause: The capability in question is not supported when the materialized view contains a column or expression in the GROUP BY clause that is not also present in the list of output select expressions.
Action: Include all GROUP BY expressions in the output select list.
QSM-02005: named view in FROM list
Cause: The capability in question is not supported when a named view appears in the FROM list.
Action: Remove the named view from the FROM list.
QSM-02006: subquery in FROM list
Cause: The capability in question is not supported when a subquery appears in the FROM list.
Action: Remove the subquery from the FROM list.
QSM-02007: multiple instances of the same table or view
Cause: The capability in question is not supported when the same table or view occurs more than once in the FROM list.
Action: Re-phrase the query to avoid multiple instances of the same table. For instance,
QSM-02008: non-join filter condition in WHERE or HAVING clause
Cause: The capability in question is not supported when the materialized view has a selection condition (an expression not representing a join) in the WHERE or HAVING clauses.
Action: Remove the selection filter expression.
QSM-02009: non-inner join
Cause: The capability in question is only supported with inner joins.
Action: Re-phrase the query using an inner join. Remove any outer joins.
QSM-02010: join predicate with operator other than equals (=)
Cause: The capability in question is not supported when the materialized uses a relationship operator other than equals ("=") in a join in the WHERE clause. This is known as a non-equijoin.
Action: Re-phrase the query to avoid the non-equijoin.
QSM-02011: a HAVING clause is present
Cause: The capability in question is not supported when the materialized view uses a HAVING clause.
Action: Remove the HAVING clause.
QSM-02012: a CONNECT BY clause is present
Cause: The capability in question is not supported when the materialized view uses a CONNECT BY clause.
Action: Re-phrase the query to avoid use of the CONNECT BY clause.
QSM-02013: SELECT list includes a RAW data type expression
Cause: The capability in question is not supported when the materialized view uses RAW data type in an expression.
Action: Remove the reference to the RAW expression.
QSM-02014: GROUP BY expression other than a column
Cause: The capability in question is not supported when the materialized view uses an expression other than a simple column reference in the GROUP BY clause.
Action: Re-phrase the query to use only simple column expressions in the GROUP BY clause.
QSM-02015: Index Organized Table (IOT) present in FROM list
Cause: The capability in question is not supported when the materialized view references an Index Organized Table in the FROM list.
Action: Remove the reference to the Index Organized Table.
QSM-02016: clustered table in FROM list
Cause: The capability in question is not supported when the materialized view references a clustered table in the FROM list.
Action: Remove the reference to the clustered table in the FROM list.
QSM-02017: subquery present in the HAVING clause
Cause: The capability in question is not supported when the materialized view uses a subquery in the HAVING clause.
Action: Re-phrase the query to avoid the subquery in the HAVING clause.
QSM-02018: subquery present in the WHERE clause
Cause: The capability in question is not supported when the materialized view uses a subquery in the WHERE clause.
Action: Re-phrase the query to avoid the subquery in the WHERE clause.
QSM-02019: mv references another mv in FROM clause
Cause: The capability in question is not supported when the materialized view is nested (i.e., when it references another materialized view in its FROM list).
Action: Re-phrase the query to avoid reference to the other materialized view.
QSM-02020: container column not in SELECT list with NOT NULL constraint
Cause: The capability in question is not supported when the materialized view's container table has a column that does not correspond to an output expression in the select list, and that column has a NOT NULL constraint. This situation can result in problems during refresh since any new rows inserted into the materialized view will set that column to NULL.
Action: Disable or remove the NOT NULL constraint.
QSM-02021: set operator encountered in mv
Cause: The capability in question is not supported when the materialized view uses set operators such as UNION, UNION ALL, MINUS, etc.
Action: Re-phrase the query to avoid the use of set operators.
QSM-02022: aggregate selections
Cause: The capability in question is not supported when the materialized view uses an aggregate expression in the HAVING clause.
Action: Re-phrase the query to avoid the use of an aggregate in the HAVING clause.
QSM-02023: nested cursor
Cause: The capability in question is not supported when the materialized view uses a nested cursor expression.
Action: Re-phrase the query to avoid use of a nested cursor expression.
QSM-02024: no GROUP BY clause
Cause: The capability in question is not supported when the materialized view does not use a GROUP BY clause.
Action: Re-phrase the query to use a GROUP BY clause.
QSM-02025: no aggregate functions
Cause: The capability in question is not supported when the materialized view uses no aggregate functions.
Action: Re-phrase the query to use aggregate functions.
QSM-02026: non-AND conjunction in WHERE clause
Cause: The capability in question is not supported when the materialized view uses a conjunction other than AND (such as OR) in the WHERE clause.
Action: Re-phrase the query to avoid use of the non-AND conjunction.
QSM-02027: group by ROLLUP
Cause: The capability in question is not supported when the materialized view uses the ROLLUP operator in the GROUP BY clause.
Action: Re-phrase the query to avoid use of the ROLLUP operator.
QSM-02028: group by CUBE
Cause: The capability in question is not supported when the materialized view uses the CUBE operator in the GROUP BY clause.
Action: Re-phrase the query to avoid use of the CUBE operator.
QSM-02029: PL/SQL function invocation
Cause: The capability in question is not supported when the materialized view invokes a PL/SQL function.
Action: Re-phrase the query to avoid use of PL/SQL functions.
QSM-02030: reduced precision specified for prebuilt mv
Cause: The capability in question is not supported when the materialized view is created with the WITH REDUCED PRECISION clause.
Action: DROP the materialized view and re-create it without using the WITH REDUCED PRECISION clause.
QSM-02031: materialized view cannot support any type of query rewrite
Cause: of the problem.
Action: Examine the other messages and documentation to determine the
QSM-02032: no joins are present in the WHERE clause
Cause: The capability in question is not supported when the materialized view includes no join conditions in the WHERE clause.
Action: Re-phrase the query to include a join.
QSM-02033: no filter conditions are present in the WHERE clause
Cause: The capability in question is not supported when the materialized view includes no filter selection conditions in the WHERE clause.
Action: Add a filter condition.
QSM-02034: no joins are present in the HAVING clause
Cause: The capability in question is not supported when the materialized view includes no joins in the HAVING clause.
Action: Re-phrase the query to include a join.
QSM-02035: no filter conditions are present in the HAVING clause
Cause: The capability in question is not supported when the materialized view includes no filter condition in the HAVING clause.
Action: Re-phrase the query to include a join.
QSM-02036: in-list present in mv
Cause: The capability in question is not supported when the materialized view uses an IN list.
Action: Re-phrase the query to avoid the use of IN lists.
QSM-02037: cannot evaluate constant expression at compile time
Cause: The capability in question is not supported when the materialized view uses a compile-time non-constant expression in a filter condition in the WHERE or HAVING clauses. For example, WHERE X=1 uses a compile-time constant expression in a filter condition. WHERE X=MY_PLSQL_FUNCTION() uses a compile-time non-constant expression in a filter condition.
Action: Re-phrase the query to avoid the use of a compile-time non-constant expressions in filter conditions.
QSM-02038: Partition Change Tracking (PCT) is enabled
Cause: The Partition Change Tracking (PCT) capability is supported for this materialized view.
Action: No action is needed.
QSM-02039: top level mv query uses grouping sets
Cause: The capability in question is not supported when the materialized view use grouping sets.
Action: Re-phrase the query to avoid use of grouping sets.
QSM-02040: top level query contains GSets and the key is too long for rewrite
Cause: The capability in question is not supported when the materialized view uses a grouping set with too many keys.
Action: Reduce the number of grouping set keys.
QSM-02041: nested aggregate function
Cause: The capability in question is not supported when the materialized view nests an aggregate function invocation as an argument to another aggregate function.
Action: Re-phrase the query to avoid the nested aggregate function invocation.
QSM-02042: view or subquery in from list
Cause: The capability in question is not supported when the materialized view references a view or subquery in the FROM list.
Action: Re-phrase the query to avoid the use of views or subqueries in in the FROM list.
QSM-02044: ORDER BY clause in mv
Cause: The capability in question is not supported when the materialized view includes an ORDER BY clause.
Action: Remove the ORDER BY clause.
QSM-02045: START WITH clause in mv
Cause: The capability in question is not supported when the materialized view includes a START WITH clause.
Action: Re-phrase the query to avoid the use of the START WITH clause.
QSM-02047: window function in mv
Cause: The capability in question is not supported when the materialized view uses a window function.
Action: Re-phrase the query to avoid the use of window functions.
QSM-02048: outer join in mv
Cause: The capability in question is not supported when the materialized view uses an outer join.
Action: Re-phrase the query to avoid the use of outer joins.
QSM-02049: subquery using the ANY clause in mv
Cause: The capability in question is not supported when the materialized view uses the ANY clause with a subquery.
Action: Re-phrase the query to avoid the use of the ANY clause.
QSM-02050: subquery using the ALL clause in mv
Cause: The capability in question is not supported when the materialized view uses the ALL clause with a subquery.
Action: Re-phrase the query to avoid the use of the ALL clause.
QSM-02051: subquery using the NOT EXISTS clause in mv
Cause: The capability in question is not supported when the materialized view uses the NOT EXISTS with a subquery.
Action: Re-phrase the query to avoid the use of the NOT EXITS clause.
QSM-02052: subquery using a select list in mv
Cause: The capability in question is not supported when the materialized view uses a select list.
Action: Re-phrase the query to avoid the use of a select list.
QSM-02053: collection subquery in mv
Cause: The capability in question is not supported when the materialized view uses a collection subquery.
Action: Re-phrase the query to avoid the use of collection subqueries.
QSM-02054: DISTINCT clause in select list in mv
Cause: The capability in question is not supported when the materialized view uses the DISTINCT clause in the select list.
Action: Re-phrase the query to avoid the use of the DISTINCT clause.
QSM-02055: mv references a packed object table or view
Cause: The capability in question is not supported when the materialized view references a packed object table or view.
Action: Re-phrase the query to avoid the use of the packed object tables or views.
QSM-02056: correlated variable and outer join in mv
Cause: The capability in question is not supported when the materialized view uses a correlated variable and an outer join.
Action: Re-phrase the query to avoid the use of the correlated variables or outer joins.
QSM-02057: ROWNUM referenced in mv
Cause: The capability in question is not supported when the materialized view references the ROWNUM function.
Action: Re-phrase the query to avoid the use of the ROWNUM function.
QSM-02058: set operator in mv and compatibility mode is less than 9.0
Cause: The capability in question is not supported when the materialized view uses a set operator and the compatibility mode is less than 9.0.
Action: Re-phrase the query to avoid the use of set operators or set the compatibility mode to 9.0 or greater.
QSM-02059: join may produce duplicate rows in mv
Cause: The capability in question is not supported when the materialized view contains a join condition that can result in duplicate rows in the materialized view.
Action: Re-phrase the query to avoid the occurrence of duplicate rows in the materialized view.
QSM-02061: one or more joins present in mv
Cause: The capability in question is not supported when the materialized view contains joins.
Action: Re-phrase the query to avoid the use of the joins.
QSM-02062: GROUP BY clause in mv
Cause: The capability in question is not supported when the materialized view uses the GROUP BY clause.
Action: Re-phrase the query to avoid the use of the GROUP BY clause.
QSM-02063: aggregate function in mv
Cause: The capability in question is not supported when the materialized view uses an aggregate function.
Action: Re-phrase the query to avoid the use of the aggregate functions.
QSM-02064: subquery in mv
Cause: The capability in question is not supported when the materialized view uses a subquery.
Action: Re-phrase the query to avoid the use of the subqueries.
QSM-02066: Oracle error: see RELATED_NUM and RELATED_TEXT for details
Cause: The capability in question is not supported because an attempt to create the materialized view would result in an error.
Action: Examine the associated Oracle error code in the RELATED_NUM column and the Oracle error text in the RELATED_TEXT column and address the problem.
QSM-02067: no partition key or PMARKER or join dependent expression in select list
Cause: The capability in question is not supported when the materialized view unless the select list (and group by list if a GROUP BY clause is present) includes the partition key or PMARKER function reference to the table in question or an expression join dependent on the partitioning column of the table in question.
Action: Add the partition key or a PMARKER function reference or a join dependent expression to the select list (and the GROUP BY clause, if present).
QSM-02068: relation is not a partitioned table
Cause: The capability in question is not supported when the relation in question is not a partitioned table.
Action: Change the query to reference a partitioned table.
QSM-02069: PCT not supported with multi-column partition key
Cause: The capability in question is not supported when the table in is partitioned on a multi-column key.
Action: Re-phrase the query to reference a table partitioned on a single column key.
QSM-02070: PCT not supported with this type of partitioning
Cause: The capability in question is not supported when the table in question uses certain types of partitioning.
Action: Re-phrase the query to reference a table that is uses a type of partitioning that is supported for this capability.
QSM-02071: internal error: undefined PCT failure code
Cause: An internal Oracle error has occurred.
Action: Report the problem through your normal support channels.
QSM-02072: requirements not satisfied for fast refresh of nested mv
Cause: The capability in question is not supported because one or more of the requirements for this capability have not been satisfied.
Action: Examine the relevant nested materialized view documentation in the Warehouse Guide and address the problem.
QSM-02073: non-primary key RepAPI mv is not fast refreshable
Cause: Fast refresh is supported for RepAPI materialized views only if it is also a primary key materialized view.
Action: Re-design the materialized view to be a primary key materialized view.
QSM-02074: materialized view over Heterogeneous Services link
Cause: The capability in question is not supported when the materialized view uses a heterogeneous link.
Action: Re-design the materialized view to avoid the use of the heterogeneous links.
QSM-02075: materialized view on synonym
Cause: The capability in question is not supported when the materialized view references a synonym, if the compatible parameter is earlier than 10.2.0.
Action: Re-phrase the query to avoid the use of the synonyms.
QSM-02076: sequence number in the mv log is newer than last refresh
Cause: The timestamp of the sequence number in the mv log was after the last refresh time.
Action: A complete refresh is required before the next fast refresh.
QSM-02077: mv log is newer than last full refresh
Cause: The capability in question is not supported when the relevant materialized view log was created after the creation or most recent complete refresh of the materialized view.
Action: Perform a complete refresh of the materialized view.
QSM-02078: mv log must have new values
Cause: The capability in question is not supported when the relevant materialized view log omits new values.
Action: Re-create the materialized view log using the NEW VALUES clause.
QSM-02079: mv log must have ROWID
Cause: The capability in question is not supported when the relevant materialized view log omits ROWIDs.
Action: Re-create the materialized view log using the ROWID clause.
QSM-02080: mv log must have primary key
Cause: The capability in question is not supported when the relevant materialized view log omits primary keys.
Action: Re-create the materialized view log using the PRIMARY KEY clause.
QSM-02081: mv log does not have all necessary columns
Cause: The capability in question is not supported when the relevant materialized view log omits columns referenced in the select list of the materialized view.
Action: Re-create the materialized view log and include all columns referenced in the select list.
QSM-02082: problem with mv log
Cause: The capability in question is not supported because of a problem the materialized view log in question.
Action: Examine the relevant materialized view log and fast refresh documentation in the Warehouse Guide and address the problem.
QSM-02083: mv references PL/SQL function that maintains state
Cause: The capability in question is not supported when the materialized view references a PL/SQL function that maintains state and which may not return the same value every time it is invoked against the same set of rows.
Action: Re-phrase the query to avoid such a PL/SQL function. Or modify the PL/SQL function to avoid state maintenance and change its declaration accordingly.
QSM-02084: DISTINCT clause on a duplicate sensitive aggregate function
Cause: The capability in question is not supported when the materialized view uses the DISTINCT clause in this context.
Action: Re-phrase the query to avoid the use of the DISTINCT clause.
QSM-02086: mv uses the MIN or MAX aggregate functions
Cause: The capability in question is not supported when the materialized view uses the MIN or MAX function.
Action: Re-phrase the query to avoid the use of the MIN or MAX functions.
QSM-02088: mv omits at least one grouping key from the select list
Cause: The capability in question is not supported when the materialized view omits any grouping expressions from the select list.
Action: Include all GROUP BY expressions in the select list.
QSM-02090: SELECT includes an expression that is not just a column
Cause: The capability in question is not supported when the materialized view uses an expression in the select list that is not a simple column reference.
Action: Re-phrase the query to avoid the use of the expressions that are not simple column references.
QSM-02091: mv references a non-repeatable or session-sensitive expression
Cause: The capability in question is not supported when the materialized view uses an expression that may not return the same value each time it is invoked against the same set of rows or that may return different values depending on session parameters.
Action: Re-phrase the query to avoid the use of such expressions.
QSM-02092: mv references a sequence number
Cause: The capability in question is not supported when the materialized view references a sequence number.
Action: Re-phrase the query to avoid the reference to sequence numbers.
QSM-02093: mv uses an object REF clause
Cause: The capability in question is not supported when the materialized view uses an object REF clause.
Action: Re-phrase the query to avoid the use of an object REF clause.
QSM-02096: mv references a named view
Cause: The capability in question is not supported when the materialized view references a view.
Action: Re-phrase the query to avoid references to views.
QSM-02099: mv references a remote table or view in the FROM list
Cause: The capability in question is not supported when the materialized view references a remote table or view in the FROM list.
Action: Re-phrase the query to avoid references to remote tables or views.
QSM-02101: mv references a synonym in the FROM list
Cause: The capability in question is not supported when the materialized view references a synonym in the FROM list.
Action: Re-phrase the query to avoid the reference to the synonym.
QSM-02102: mv FROM list references an object in the SYS schema
Cause: The capability in question is not supported when the materialized view references an object in the SYS schema.
Action: Re-phrase the query to avoid the reference to the SYS schema.
QSM-02104: aggregate function in a filter condition in the HAVING clause
Cause: The capability in question is not supported when the materialized view references an aggregate function in a filter condition in the HAVING clause.
Action: Re-phrase the query to avoid the use of aggregates in filter conditions in the HAVING clause.
QSM-02106: mv uses a filter condition in the WHERE or HAVING clause
Cause: The capability in question is not supported when the materialized view includes a filter condition in the WHERE or HAVING clause.
Action: Re-phrase the query to avoid the use of filter conditions in the WHERE or HAVING clauses.
QSM-02112: top level query has LEFT OUTER, RIGHT OUTER or FULL OUTER join
Cause: The capability in question is not supported when the materialized view uses these types of joins.
Action: Re-phrase the query to avoid the use of these types of joins.
QSM-02113: expression in select list references multiple tables or views
Cause: The capability in question is not supported when the materialized view includes an expression in the select list that references multiple tables or views.
Action: Re-phrase the query to avoid the use of the such expressions.
QSM-02114: no GROUP BY clause, no aggregates and not >= 9.0 compatibility
Cause: The capability in question is not supported when the materialized view has no GROUP BY clause, no aggregates and compatibility mode is less than 9.0.
Action: Re-phrase the query to avoid the include a GROUP BY clause or an aggregate function. Or set compatibility mode to 9.0 or greater.
QSM-02115: mv references a remote object and is refreshed ON COMMIT
Cause: The capability in question is not supported when the materialized view references a remote object and is refreshed ON COMMIT.
Action: Re-phrase the query to avoid the reference to the remote object or alter the materialized view to be refreshed ON DEMAND.
QSM-02116: mupltiple master sites
Cause: The capability in question is not supported when the materialized view references multiple remote objects that reside at different remote instances.
Action: Re-phrase the query to avoid the use of multiple master sites.
QSM-02117: missing GROUPING_ID or GROUPING functions on GROUP BY column(s)
Cause: The capability in question is not supported when the materialized view uses grouping sets but omits the relevant GROUPING_ID or GROUPING functions.
Action: Re-phrase the query to include the relevant GROUPING_ID or GROUPING functions.
QSM-02118: duplicate grouping sets
Cause: The capability in question is not supported when the materialized view redundantly references grouping sets.
Action: Re-phrase the query to avoid the use of the redundant grouping sets.
QSM-02119: internal error while analyzing required supporting aggregates
Cause: An internal Oracle error has occurred.
Action: Report the problem through your normal support channels.
QSM-02120: compatibility mode must be 9.0 or higher
Cause: The capability in question is not supported when the compatibility mode is less than 9.0.
Action: Set the compatibility mode to 9.0 or higher.
QSM-02121: set operator in a context not supported for fast refresh
Cause: The capability in question is not supported when the materialized view uses a set operator in this context.
Action: Re-phrase the query to avoid the use of the set operator.
QSM-02122: compatibility mode must be 8.1 or higher
Cause: The capability in question is not supported when the compatibility mode is less than 8.1.
Action: Set the compatibility mode to 8.1 or higher.
QSM-02123: subquery and UNION mv's must be primary key mv's
Cause: The capability in question is not supported when the materialized view is not a primary key materialized view and uses subqueries or the union operator in this context.
Action: Re-create the materialized view as a primary key materialized view.
QSM-02124: object type in WHERE clause
Cause: The capability in question is not supported when the materialized view references an object type in the WHERE clause.
Action: Re-phrase the query to avoid the reference to the object type.
QSM-02125: subquery join conditions don't meet requirements for capability
Cause: The capability in question is not supported when the materialized view uses a subquery in a join in this way.
Action: Examine the relevant replication documentation concerning subquery materialized views and address the problem.
QSM-02126: no rowid at master site
Cause: The capability in question is not supported when the materialized view references a remote site that does not support rowids.
Action: Re-phrase the query to avoid the reference to the remote site.
QSM-02127: not supported for this type mv by Oracle version at master site
Cause: The capability in question is not supported when the materialized view uses certain constructs and references an older version, remote Oracle instance.
Action: Re-phrase the query to avoid the use of the construct or upgrade the remote Oracle instance.
QSM-02128: does not meet the requirements of a primary key mv
Cause: The capability in question is not supported when the materialized view fails to meet the requirements of a primary key materialized view.
Action: Examine the relevant primary key materialized view replication documentation and address the problem.
QSM-02129: join or filter condition(s) are complex
Cause: The capability in question is not supported when the materialized view uses a complex join or filter condition.
Action: Re-phrase the query to simplify the join or filter condition.
QSM-02130: expression not supported for fast refresh
Cause: The capability in question is not supported when the materialized view references certain, complex expressions.
Action: Re-phrase the query to simplify the expression.
QSM-02131: agg(expr) requires correspondng SUM(expr) function
Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the SUM function on the same argument.
Action: Add the SUM function to the select list.
QSM-02132: agg(expr) requires correspondng COUNT(expr) function
Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the COUNT function on the same argument.
Action: Add the COUNT function to the select list.
QSM-02133: agg(expr) requires correspondng MIN(expr) function
Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the MIN function on the same argument.
Action: Add the MIN function to the select list.
QSM-02134: agg(expr) requires correspondng MAX(expr) function
Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the MAX function on the same argument.
Action: Add the MAX function to the select list.
QSM-02135: agg(expr) requires correspondng AVG(expr) function
Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the AVG function on the same argument.
Action: Add the AVG function to the select list.
QSM-02136: agg(expr) requires correspondng VARIANCE(expr) function
Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the VARIANCE function on the same argument.
Action: Add the VARIANCE function to the select list.
QSM-02137: agg(expr) requires correspondng STDDEV(expr) function
Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the STDDEV function on the same argument.
Action: Add the STDDEV function to the select list.
QSM-02138: agg(expr) requires correspondng agg(expr*expr) function
Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of that same aggregate function on the square of the same argument.
Action: Add an invocation of the same aggregate function on the square of the same argument (that is, the argument multiplied by itself).
QSM-02139: agg(expr) requires correspondng agg(expr+expr) function
Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of that same aggregate function on the same argument added to the same argument.
Action: Add the indicated aggregate function to the select list.
QSM-02140: agg(expr) requires correspondng SUM(expr*expr) function
Cause: The capability in question is not supported when the materialized view uses certain aggregate functions but omits an invocation of the SUM function on the square of the same argument (the argument multiplied by itself).
Action: Add the SUM function on the square of the argument.
QSM-02141: the reason why the capability is disabled has escaped analysis
Cause: The EXPLAIN_MV analysis engine has failed to capture the reason why the given capability is not possible.
Action: Report the problem through your normal problem reporting channels.
QSM-02142: COUNT(*) is not present in the select list
Cause: The materialized view query omits COUNT(*) from the select list.
Action: Add COUNT(*) to the select list.
QSM-02143: SUM(expr) without COUNT(expr)
Cause: SUM(expr) occurs in the select list without a corresponding COUNT(expr).
Action: Add COUNT(expr) to the select list.
QSM-02144: aggregate functions are present without a GROUP BY clause
Cause: One or more aggregate functions are present in the select list but a GROUP BY clause is not used.
Action: Add a GROUP BY clause.
QSM-02145: GROUP BY clause is present but no aggregate functions are used
Cause: A GROUP BY clause is used but no aggregate functions are present in the select list.
Action: Add an aggregate function to the select list.
QSM-02146: see the reason why REFRESH_FAST_AFTER_INSERT is disabled
Cause: REFRESH_FAST_AFTER_ONETAB_DML is disabled for the same reason that REFRESH_FAST_AFTER_INSERT is disabled.
Action: Correct the problem with REFRESH_FAST_AFTER_INSERT.
QSM-02147: default date format is sensitive to session settings
Cause: You have specified a date conversion operation using either the default format or an incomplete format. The default date format or an incomplete format is sensitive to session settings, and therefore may not be reproducible across different environments.
Action: Specify a complete date format string.
QSM-02148: many to many subquery joins require 9.0 compatibility or higher
Cause: You have specified a many to many join in your materialized view while running in less than 9.0 compatibility mode.
Action: Set your compatibility mode to 9.0 or higher or restructure the materialized view query.
QSM-02149: ON COMMIT with this MV requires 9.0 compatibility or higher
Cause: You have specified a materialized view that uses some combination of the following: joins aggregation filter conditions in the WHERE clause a remote relation in the FROM list a SUM(x) function without a corresponding COUNT(x) function an omitted COUNT(*) aggregate function a MIN() or MAX() aggregate function in combination with the REFRESH ON COMMIT option while running in less than 9.0 compatibility mode.
Action: Set your compatibility mode to 9.0 or higher or restructure the materialized view query.
QSM-02150: select lists must be identical across the UNION operator
Cause: You have specified a materialized view using the UNION operator and the respective queries on each side of the UNION operator do not have the same select list. The RELATED_NAME column shows the alias of the first different select list item. The RELATED_NUM column shows the offset from the SELECT keyword to the start of this select list item.
Action: Restructure the materialized view query such that the respective sides of the UNION operator have identical select lists.
QSM-02151: subquery or named view in FROM list and < 9.0 compatibility
Cause: You have specified a materialized view that references a subquery or named view in its top level FROM list while running in less than 9.0 compatibility mode.
Action: Set compatibility mode to 9.0 or higher or restructure the materialized view query.
QSM-02152: subquery or named view in FROM list even after view merging
Cause: You have specified a materialized view that references a subquery ore named view in its top level FROM list that could not be merged during the view merging process.
Action: Restructure the materialized view query.
QSM-02153: inline view or subquery in FROM list not supported for this type MV
Cause: You have specified a materialized view that references an inline view or a subquery. The indicated capability is not supported for this type of materialized view.
Action: Restructure the materialized view query.
QSM-02154: MV is not fast refreshable even with view merging
Cause: You have a materialized view with view in the FROM clause, however it does not meet the criteria for fast refresh after view merging.
Action: Restructure the materialized view query to remove the offending view or the complex construct in the view.
QSM-02161: see the reason why REFRESH_FAST_AFTER_ONETAB_DML is disabled
Cause: REFRESH_FAST_AFTER_ANY_DML is disabled for the same reason that REFRESH_FAST_AFTER_ONETAB_DML is disabled.
Action: Correct the problem with REFRESH_FAST_AFTER_ONETAB_DML.
QSM-02162: the detail table does not have a materialized view log
Cause: The fast refresh cannot be performed because the master table does not contain a materialized view log.
Action: Use the CREATE MATERIALIZED VIEW LOG command to create a materialized view log on the master table.
QSM-02163: cannot use object id columns from materialized view log
Cause: The materialized view log either does not have object id columns logged, or the timestamp associated with the object id columns is more recent than the last refresh time.
Action: A complete refresh is required before the next fast refresh. Add object id columns to the materialized view log, if required.
QSM-02169: the materialized view contains partition extended table name
Cause: Fast refresh of materialized aggregate views and/or materialized join views are not supported if they were defined using partition extended table names.
Action: Create the fast refreshable materialized view without using partition extended table names or create the materialized view as a complete refresh materialized view.
QSM-02170: tables must be identical across the UNION operator
Cause: You have specified a materialized view using the UNION operator and the tables on each side of the UNION operator do not match. Fast refresh is not supported in this context.
Action: Restructure the materialized view query such that the respective sides of the UNION operator have the same table.
QSM-02171: the materialized view has a join operation in the outer UNION block
Cause: Fast refresh is not supported if a materialized view having the UNION operator contains a join operation.
Action: Rewrite the materialized view query without the join.
QSM-02173: the unique constraints does not exist on the join columns of the inner table
Cause: If there are outer joins, unique constraints must exist on the join columns of the inner table. Othwerwise, the materialized view can not be fast refreshable.
Action: None
QSM-02174: the materialized view does not have a UNION ALL marker column
Cause: For a materialized view with UNION ALL to be fast refreshable, it must have a UNION ALL marker column. This is a constant column, at the same ordinal position in each query block and must have distinct values in each query block.
Action: Add a UNION ALL marker column to each query block in the UNION ALL query defining the materialized view.
QSM-02175: some query block in UNION ALL MV is not fast refreshable
Cause: For a materialized view with UNION ALL to be fast refreshable, each query block must conform to a fast refreshable materialized join view or materialized aggregate view.
Action: Check each query block in the UNION ALL to ensure it is either a materialized view with joins or aggregates.
QSM-02176: MV with UNION ALL in a view is too complex
Cause: If a materialized view has a view whose definition involves a UNION ALL query, then the materialized view's defining query cannot have any clauses other than SELECT or FROM. Other clauses such as WHERE, HAVING, CONNECT BY, or GROUP BY are not allowed. Further more, the FROM clause should have only one item.
Action: Remove any clauses besides SELECT and FROM from the materialized view's defining query.
QSM-02177: MV with UNION ALL in a view must match the view's SELECT list
Cause: If a materialized view has a view whose definition involves a UNION ALL query, then the materialized view's select list must match the underlying view's select list exactly. It must not have any expressions and must not have add/drop/reorder columns from the underlying view.
Action: Use select * when defining a materialized view with a UNION ALL in a view.
QSM-02178: MV has a view with UNION ALL that is not fast refreshable
Cause: The materialized view has a view whose definition involves a UNION ALL query that does not satisfy the requirements for fast refresh.
Action: Check that the defining query of the view being referenced in the materialized view satisfies conditions for fast refresh of a UNION ALL materialized view.
QSM-02179: MV with UNION ALL requires compatibility >= 9.2
Cause: The setting of the COMPATIBLE initialization parameter is less than 9.2.0.
Action: Set COMPATIBLE to 9.2.0 or higher.
QSM-02180: no primary key constraint in the master table
Cause: The explain_mview assumes that the materialized view is going to be created as the Primary Key materialized view. A Primary Key materialized view can not be created if the base table does not have a primary key constraint.
Action: Add a primary key constraint to the base table, or create the materialized view as Rowid MV by specifying the WITH ROWID option. If the materialized view is a Rowid MV, then it should be able to do complete refresh and even fast refresh, given that the materialized view log on the master table has a rowid.
QSM-02181: a SPREADSHEET clause is present
Cause: The capability in question is not supported when the materialized view uses a SPREADSHEET clause.
Action: Remove the SPREADSHEET clause.
QSM-02182: PCT is enabled through a join dependency
Cause: The capability in question is not supported when the materialized view does not contain some expression join dependent on the partitioning key of relation in question in the select list. For definition of join dependency, please look at Oracle documentation.
Action: Change the query to contain the partitioning key
QSM-02183: Expression to enable PCT not in PARTITION BY of analytic function or SPREADSHEET
Cause: The capability in question is not supported when the expression is not in the PARTITION BY clause
Action: Change the query so that the expression is in the PARTITION BY
QSM-02184: Expression to enable PCT cannot be rolled up
Cause: The capability in question is not supported when the expression is rolled up
Action: Change the query so that the expression is not rolled up
QSM-02185: no partition key or PMARKER in select list
Cause: The capability in question is not supported when the materialized view unless the select list (and group by list if a GROUP BY clause is present) includes either the partition key of or a PMARKER function reference to the table in question.
Action: Add the partition key or a PMARKER function reference to the select list (and the GROUP BY clause, if present).
QSM-02186: PARTITIONED OUTER JOIN is present
Cause: The capability in question is not supported when the materialized view has PARTITIONED OUTER JOIN.
Action: Remove PARTITIONED OUTER JOIN.
QSM-02187: materialized view on external table
Cause: The capability in question is not supported when the materialized view references an external table.
Action: Re-phrase the query to avoid the use of the external tables.
QSM-02188: named view in FROM list not supported for this type MV
Cause: You have specified a materialized view that references a named view The indicated capability is not supported for this type of materialized view.
Action: Restructure the materialized view query.
QSM-02189: materialized view definition changes
Cause: The definition of the materialized view has changed. Usually redefining the synonym or table in the definition can cause this. The materialized view can not be fast refreshed.
Action: Complete refresh or recreate the materialized view.
QSM-02190: SQL PIVOT or UNPIVOT is present
Cause: The capability in question is not supported when the materialized view has sql PIVOT or UNPIVOT operation.
Action: Remove sql PIVOT or UNPIVOT.
QSM-02191: types of MV logs are not compatible
Cause: The capability in question is not supported when the materialized view is defined on detail tables which do not have a compatible type of materialized view logs, either all timestamp based or commit SCN based.
Action: Complete refresh or recreate materialized view logs.
QSM-02192: commit SCN based MV log is not in consistent state
Cause: The capability in question is not supported when the relevant materialized view log is not in consistent state due to the failure when populating the mapping table of SYS.SNAP_XCMT$.
Action: Perform a complete refresh of the materialized view.
QSM-02193: unsupported MV on commit SCN based MV logs
Cause: The capability in question is not supported when the relevant materialized view is not supported to be defined on detail tables which have commit SCN based MV logs.
Action: None
QSM-02194: CASE expressions present in materialized view
Cause: The capability in question is not supported when the materialized view contain CASE expressions.
Action: Re-phrase the query to avoid the use of CASE expressions.
QSM-02195: PCT FAST REFRESH is not possible if query contains a named view
Cause: The capability in question was not supported because the materialized view query contained a named view.
Action: Rephrase the query to avoid the use of named views.
QSM-02196: PCT FAST REFRESH is not possible if query contains an inline view
Cause: The capability in question was not supported because the materialized view query contained an inline view.
Action: Rephrase the query to avoid the use of an inline view.
QSM-02197: PCT FAST REFRESH is not possible if query contains a remote table
Cause: The capability in question was not supported because the materialized view query contained a remote table.
Action: Rephrase the query to avoid the use of a remote table.
QSM-02198: PCT FAST REFRESH is not possible if HAVING clause includes a subquery
Cause: The capability in question was not supported because the materialized view query HAVING clause included a subquery.
Action: Rephrase the query to avoid the use of a subquery in the HAVING clause.
QSM-02199: PCT FAST REFRESH is not possible if WHERE clause includes a subquery
Cause: The capability in question was not supported because the materialized view query WHERE clause included a subquery.
Action: Rephrase the query to avoid the use of a subquery in the WHERE clause.
QSM-02200: PCT FAST REFRESH is not possible if query contains LEFT OUTER, RIGHT OUTER or FULL OUTER JOIN
Cause: The capability in question was not supported because the materialized view query contained LEFT OUTER, RIGHT OUTER or FULL OUTER JOIN.
Action: Rephrase the query to avoid the use of LEFT OUTER, RIGHT OUTER or FULL OUTER JOIN.
QSM-02201: PCT FAST REFRESH is not possible if there is a self join or self cartesian product in query
Cause: The capability in question was not supported because the materialized view query contained self join of self cartesian product in the query.
Action: Rephrase the query to avoid the use of self joins or self cartesian product in the query.
QSM-02202: PCT FAST REFRESH is not possible if query has ORDER BY clause
Cause: The capability in question was not supported because the materialized view query contained an ORDER BY clause.
Action: Rephrase the query to avoid the use of the ORDER BY clause.
QSM-02203: PCT FAST REFRESH is not possible if query has set operand query blocks
Cause: The capability in question was not supported because the materialized view query contained set operand query blocks.
Action: Rephrase the query to avoid the use of set operand query blocks.
QSM-02204: PCT FAST REFRESH is not possible if query has an inner query
Cause: The capability in question was not supported because the materialized view query contained an inner query.
Action: Rephrase the query to avoid the use of the inner query.
QSM-02205: PCT FAST REFRESH is not possible if there is a subquery inside select-list
Cause: The capability in question was not supported because the materialized view query contained a subquery inside a select-list.
Action: Rephrase the query to avoid the use of a subquery inside a select-list.
QSM-02206: PCT FAST REFRESH is not possible because this query join may produce extra duplicate rows
Cause: The capability in question was not supported because the materialized view contained a join condition that can result in duplicate rows in the materialized view.
Action: Rephrase the query to avoid the occurrence of duplicate rows in the materialized view.
QSM-02207: PCT FAST REFRESH is not possible for complex queries
Cause: The capability in question was not supported because the materialized view query was too complex.
Action: No action is necessary.
QSM-02208: subquery using the NOT IN clause in materialized view
Cause: The capability in question was not supported when the materialized view uses NOT IN with a subquery.
Action: Rephrase the query to avoid the use of the NOT IN clause.
QSM-02209: a MATCH_RECOGNIZE clause is present
Cause: The capability in question was not supported when the materialized view used a MATCH_RECOGNIZE clause.
Action: Remove the MATCH_RECOGNIZE clause.
QSM-03112: Invalid CREATE MATERIALIZED VIEW statement string
Cause: The CREATE MATERIALIZED VIEW statement that was passed into the procedure was not a valid one.
Action: Check the reason(s) following the error or the statement and retry the operation.
QSM-03113: Cannot tune the MATERIALIZED VIEW statement string
Cause: The MATERIALIZED VIEW statement could not be tuned.
Action: Check the reason(s) following the error or the statement and retry the operation.
QSM-03114: Cannot tune FOR UPDATE materialized view
Cause: The materialized view was created with the FOR UPDATE option.
Action: Rephrase the statement to avoid the use of the FOR UPDATE option.
QSM-03115: Cannot tune materialized view ON PREBUILT table
Cause: The materialized view was created on a prebuilt table.
Action: Rephrase the statement to avoid the use of the ON PREBUILT option.
QSM-03116: The materialized view is already optimal and cannot be tuned any further
Cause: The materialized view has the capabilities that are specified in the statement.
Action: None
QSM-03117: Cannot tune the materialized view to be fast refreshable
Cause: The materialized view could not be tuned or decomposed to be fast refreshable.
Action: Run the dbms_mview.explain_mview to find out the reason.
QSM-03118: Cannot tune the materialized view for general rewrite
Cause: The materialized view could not be tuned for supporting general rewrite.
Action: Run the dbms_mview.explain_mview to find out the reason.
QSM-03119: The WHERE/HAVING clause is too complex for general query rewrite
Cause: The WHERE/HAVING was too complex for general rewrite.
Action: Try to simplify the WHERE/HAVING clause in the materialized view defining query.
QSM-03120: Cannot create materialized view log on encrypted columns
Cause: There were encrypted columns in materialized view defining query.
Action: Try to remove the encrypted columns in the materialized view defining query.
QSM-03201: The table string.string is classified as a fact table.
Cause: This table has met the criteria of a fact table for the purposes of synchronous refresh.
Action: None. This is an informational message.
QSM-03202: The table string.string is classified as a dimension table.
Cause: This table has met the criteria of a dimension table for the purposes of synchronous refresh.
Action: None. This is an informational message.
QSM-03203: The table string.string is classified as neither a fact nor a dimension table.
Cause: This table has not met the necessary criteria of a fact table or a dimension table for the purposes of synchronous refresh. Synchronous refresh requires that the defining query of a materialized view conform to either the star or snowflake schema. A table can be either a fact or dimension table.
Action: Check the joins of the query to ensure they conform to the requirements.
QSM-03204: The materialized view passes the join graph eligibility check for synchronous refresh.
Cause: The defining query of the materialized view (MV) conformed to the star or snowflake schema and, therefore, was eligible for synchronous refresh.
Action: None. This is an informational message.
QSM-03205: The materialized view fails the join graph eligibility check for synchronous refresh.
Cause: The defining query of the materialized view (MV) did not conform to the star or snowflake schema and, therfore, was not eligible for synchronous refresh.
Action: Check the joins of the query to ensure they conform to the requirements.
QSM-03206: The fact table is partitioned by string and its partition key is string.
Cause: The fact table had the indicated partitioning method and key.
Action: None. This is an informational message.
QSM-03207: The materialized view is partitioned by string and its partition key is string.
Cause: The materialized view (MV) had the indicated partitioning method and key.
Action: None. This is an informational message.
QSM-03208: The partition key of the fact table functionally determines the partition key of the materialized view.
Cause: The analysis by synchronous refresh indicated that the partition key of the fact table functionally determined the partition key of the materialized view (MV), which is a requirement for synchronous refresh eligibility.
Action: None. This is an informational message.
QSM-03209: The materialized view passes the partition key dependency eligibility check for synchronous refresh.
Cause: The analysis by synchronous refresh indicated that the materialized view (MV) passed the partition key dependency eligibility check.
Action: None. This is an informational message.
QSM-03210: The materialized view does not pass the partition key functional dependency check and is not eligible for synchronous refresh.
Cause: The analysis by synchronous refresh indicated that the materialized view (MV) did not pass the partition key dependency eligibility check.
Action: Check the partition keys of both the fact table and materialized view and check the joins of the materialized view to ensure the functional dependency check passes.
QSM-03211: The partition key of the MV can be rolled up from the partition key of the fact table by a join between the fact table and the dimension table string.
Cause: The analysis by synchronous refresh indicated there was a rollup relationship between the partition keys of the fact table and the materialized view (MV).
Action: None. This is an informational message.
QSM-03212: The partition key of the MV corresponds to string column of the fact table and not to the partition key of the fact table.
Cause: The analysis by synchronous refresh indicated that the the partition key of the materialized view (MV) was related to a column of the fact table and not to the partition key of the fact table.
Action: Check the partition keys of both the fact table and materialized view and and check the joins of the materialized view to ensure the functional dependency check passes.
QSM-03213: The partition key of the MV corresponds to the partition key of the fact table.
Cause: The analysis by synchronous refresh indicated that the partition key of the materialized view (MV) is the same as the partition key of the fact table.
Action: None. This is an informational message.
QSM-03214: The partition key of the MV is derived from table string whereas the partition key of the fact table is related by a join to dimension table string.
Cause: The analysis by synchronous refresh indicated that the partition key of the materialized view (MV) was related to a column of a dimension table that was not the dimension table to which the partition key of the fact table was joined.
Action: Check the partition keys of both the fact table and materialized view and check the joins of the materialized view to ensure the functional dependency check passes.
QSM-03215: The partition key of the MV is not a column related to the partition key of the fact table.
Cause: The analysis by synchronous refresh indicated that the partition key of the materialized view (MV) was not a column related to the partition key of the fact table.
Action: Check the partition keys of both the fact table and materialized view and check the joins of the materialized view to ensure the functional dependency check passes.
QSM-03216: The partition key of the MV is related to the partition key of the fact table by a join between the fact table and the dimension table string.
Cause: The analysis by synchronous refresh indicated that the partition key of the materialized view (MV) was related to the partition key of the fact table by a join.
Action: None. This is an informational message.
QSM-03217: The table string.string is classified as both a fact and a dimension table.
Cause: This table has met the necessary criteria of both a fact table and a dimension table for the purposes of synchronous refresh. Synchronous refresh requires that the defining query of a materialized view conform to either the star or snowflake schema. A table can be either a fact or dimension table.
Action: Check the joins of the query to ensure they conform to the requirements.
QSM-03218: More than one table is classified as a fact table.
Cause: More than one of the base tables of the materialized view was classified as a fact table for the purposes of synchronous refresh, which requires exactly one fact table. Synchronous refresh requires that the defining query of a materialized view conform to either the star or snowflake schema. A table can be either a fact or dimension table. However, only one (and exactly one) can be fact table and the rest must be dimension tables.
Action: Check the joins of the query to ensure they conform to the requirements.
QSM-03219: The materialized view is not partitioned and therefore is not eligible for synchronous refresh.
Cause: The materialized view was not partitioned and therefore was not eligible for synchronous refresh.
Action: Partition the materialized view so that it is eligible for synchronous refresh.
QSM-03220: The partition key of the MV belongs to a table other than the fact table.
Cause: The analysis by synchronous refresh indicated that the partition key of the materialized view (MV) was related to a table other than the fact table.
Action: Check the partition keys of both the fact table and materialized view and the check the joins of the materialized view to ensure the functional dependency check passes.
QSM-03221: The partition key of the fact table does not appear in the joins of the MV.
Cause: The analysis by synchronous refresh indicated that the partition key of the fact table did not appear in the joins of the materialized view (MV).
Action: Check the partition keys of both the fact table and materialized view and the joins.
QSM-03222: The partition key of the fact table could not be related to the partition key of the MV.
Cause: The analysis by synchronous refresh indicated that the partition key of the fact table cannot be related to the partition key of the materialized view (MV).
Action: Check the partition keys of both the fact table and materialized view and the joins.
QSM-03223: The partition method used in the table or MV is not supported by MV synchronous refresh.
Cause: An attempt was made to do synchronous refresh on a table or materialized view (MV) that used an unsupported partition method.
Action: Check the partition method used in the table or MV definition to make sure it is either range, range-range, range-list, or range-hash partition.
QSM-03224: rows being deleted or updated not in the base table
Cause: The staging log rows to be updated or deleted were not in the base table.
Action: Change the staging log key in the staging log table.
QSM-03225: rows being inserted in the base table
Cause: The staging log rows to be inserted were in the base table.
Action: Change the staging log key in the staging log table.
QSM-03226: Rows being updated had exactly the same old and new values on all columns.
Cause: The staging log rows to be updated had exactly the same old and new values on all columns.
Action: Change some of the column values of the rows being updated or delete the problematic rows from the staging log.
QSM-03227: The USING TRUSTED CONSTRAINTS clause is not specified in the materialized view definition.
Cause: The USING TRUSTED CONSTRAINTS clause was not specified in the materialized view (MV) definition. Therefore, the MV was not eligible for synchronous refresh.
Action: Alter the materialized view to use trusted constraints.
QSM-03228: The refresh option specified in the materialized view definition is not supported.
Cause: The refresh option specified in the materialized view (MV) definition was not supported for synchronous refresh. The only refresh option supported for synchronous refresh is REFRESH FORCE.
Action: Alter the materialized view refresh option to REFRESH FORCE.
QSM-03229: The ON COMMIT refresh option is not supported.
Cause: The ON COMMIT refresh option specified in the materialized view definition was not supported for synchronous refresh. The only refresh option supported for synchronous refresh is ON DEMAND.
Action: Alter the materialized view refresh option to ON DEMAND.
QSM-03230: The materialized view is in an invalid state or not fresh.
Cause: The materialized view was in an invalid state or not fresh. Synchronous refresh requires the materialized view (MV) to be in a valid and fresh state when it is registered or prepared.
Action: Recompile the MV and refresh it to esnure it is valid and fresh.
QSM-03231: ROWID is not allowed in the materialized view registered for synchronous refresh.
Cause: ROWID was used in the defining query of the materialized view.
Action: Remove the ROWID column from the defining query of the materialized view.
QSM-03232: RAW data type is not allowed in the materialized view registered for synchronous refresh.
Cause: RAW data type was used in the defining query of the materialized view.
Action: Remove the RAW data type column from the defining query of the materialized view.
QSM-03233: MIN or MAX is not allowed in the materialized view registered for synchronous refresh.
Cause: MIN or MAX was used in the defining query of the materialized view.
Action: Remove the MIN or MAX expression from the defining query of the materialized view.
QSM-03234: Set operator is not allowed in the materialized view registered for synchronous refresh.
Cause: The set operator was used in the defining query of the materialized view.
Action: Remove the set operator from the defining query of the materialized view.
QSM-03235: OUTER JOIN is not allowed in the materialized view registered for synchronous refresh.
Cause: OUTER JOIN was used in the defining query of the materialized view.
Action: Remove OUTER JOIN from the defining query of the materialized view.
QSM-03236: Subquery is not allowed in the materialized view registered for synchronous refresh.
Cause: A subquery was used in the defining query of the materialized view.
Action: Remove the subquery from the defining query of the materialized view.
QSM-03237: Trigger is not allowed in the base table string.string for synchronous refresh.
Cause: A trigger was used in the base table for synchronous refresh.
Action: Remove the trigger from the base table.
QSM-03238: The materialized view was not defined on the base table string.string for synchronous refresh.
Cause: There was no materialized view defined on the base table.
Action: Change the base table name.
QSM-03239: Group by CUBE, ROLLUP, or grouping-sets was not allowed in the materialized view registered for synchronous refresh.
Cause: A group by CUBE, ROLLUP, or grouping-sets was used in the defining query of the materialized view.
Action: Remove the group by CUBE, ROLLUP, or grouping-sets from the defining query of the materialized view.
QSM-03240: The object string.string used in a materialized view definition was not a table.
Cause: An object was used in the defining query of the materialized view, which was not a table type.
Action: Remove the object from the defining query of the materialized view.
QSM-03241: Currently there is no active operation on the specified synchronous refresh group.
Cause: Either EXECUTE_REFRESH or ABORT_REFRESH returned an error because there was no active operation on the specified synchronous refresh group.
Action: Check the catalog views to determine the status of the synchronous refresh group.
QSM-03242: The synchronous refresh group is in an invalid state for the requested operation.
Cause: Either PREPARE_REFRESH or EXECUTE_REFRESH returned an error because the specified operation was not valid for the specified synchronous refresh group.
Action: Check the catalog views to determine the status of the synchronous refresh group. Refer to the synchronous refresh documentation to find out which refresh operations are valid in the various possible states of the group.
QSM-03243: The synchronous refresh group cannot resume execution.
Cause: EXECUTE_REFRESH returned an error because all possible refresh subgroups had been processed and had a status of either COMPLETE or ABORT.
Action: Check the catalog views to determine the status of the synchronous refresh group and its objects. Refer to the synchronous refresh documentation to find out which refresh operations are valid in the various possible states of the group.
QSM-03244: The partition operations registered on table string.string are not valid.
Cause: Either an illegal partition operation was specified in the register partition operation or the partition name was incorrectly specified.
Action: Check that the partition_name belongs to a valid partition and that only one operation is registered for a partition.
QSM-03245: The partition operations registered on partition string of table string.string conflict with the data supplied in the staging logs.
Cause: The staging log contained changes to rows in the partition that were being registered. These changes occur due to changes specified in the staging log of the fact table or because of updates to dimension tables.
Action: Resolve these conflicts by either unregistering the partition or deleting the rows from the named partition in the staging log of the fact table. If the conflicts are due to dimension updates, provide all changes to the fact table in the staging log rather than attempting to register the partition operations directly.
QSM-03246: The owner of outside partition string is string whereas it should be string.
Cause: When registering the outside table, the user supplied the incorrect owner for the outside table.
Action: Unregister the outside table and register it with the correct owner, which should be the same as the owner of the base table.
QSM-03247: The staging log on table string.string has not been prepared.
Cause: PREPARE_REFRESH failed because the staging log for the specified table was not prepared with PREPARE_STAGING_LOG. All staging logs of tables of the group must be prepared before running PREPARE_REFRESH.
Action: Run PREPARE_STAGING_LOG on the specified table. Check that all other tables in the group have been prepared.
QSM-03248: The materialized view string.string is already registered.
Cause: The specified materialized view (MV) has already been registered. A MV can be registered only once.
Action: No action is necessary if the MV is in a valid state. If the MV is in an invalid state, unregister the MV and re-register it with REGISTER_MVIEWS.
QSM-03249: The table string.string does not have a staging log.
Cause: REGISTER_MVIEWS failed because the staging log for the specified table belonging to the materialized view (MV) being registered did not exist. All tables on a MV are required to have staging logs created on them for the MV to be registered for synchronous refresh.
Action: Create the staging log with the CREATE MATERIALIZED VIEW LOG statement with the FOR SYNCHRONOUS REFRESH clause. If the table already has an ordinary MV log, use the ALTER MATERIALIZED VIEW LOG instead.
QSM-03250: The fact table string.string is not referenced by any MV in the group and the changes to dimension tables contain deletes or updates.
Cause: PREPARE_REFRESH found that there was no materialized view (MV) registered for synchronous refresh that contained the specified fact table as one of its base tables and the changes to the dimension tables contained updates or deletes. This error will not occur if the changes to the dimension tables contain only inserts.
Action: There are many ways to handle this situation. Refer to the documentation for details. One way is to unregister all MV's, drop staging logs on the tables or alter them to ordinary logs and apply the changes to the tables. Then the MV's can be refreshed using conventional methods instead of synchronous refresh. If desired, the staging logs on the tables can be re-created and the MV's can be registered for synchronous refresh. Another way is to register a MV which references the specified fact table for synchronous refresh. If no such MV exists, the user can first create one before registering it.
QSM-03251: The fact table string.string is not referenced by any MV in the group and its staging log is not empty.
Cause: PREPARE_REFRESH found that there is no materialized view (MV) registered for synchronous refresh that contained the specified fact table as one of its base tables and the staging log for that table specified changes to it. PREPARE_REFRESH supports fact tables without MV's defined on them if they meet two conditions: a) the staging log for the fact table is empty; b) the staging logs for the dimension tables in the group do not specify deletes or updates.
Action: There are many ways to handle this situation. Refer to the documentation for details. Briefly, the two main ways are:

1. Register a MV which references the fact table for synchronous refresh. If no such MV exists, you can create one.

2. Unregister all the MVs in the group; drop staging log on the table or alter it to an ordinary MV log. Re-register the MVs which have been unregistered.

QSM-03252: The synchronous refresh group of table string.string is locked by another operation.
Cause: Either REGISTER_PARTITION_OPERATION or UNREGISTER_PARTITION_OPERATION detected that the synchronous refresh group to which the table belonged had been locked by another synchronous refresh operation.
Action: Wait for the other operation to complete before attempting this operation again.
QSM-03253: The synchronous refresh group of table string.string has been unlocked by another operation.
Cause: Either REGISTER_PARTITION_OPERATION or UNREGISTER_PARTITION_OPERATION detected that the synchronous refresh group to which the table belonged had been unlocked by another synchronous refresh operation. This is an internal error.
Action: Contact Oracle Support Services for assistance.
QSM-03254: The lock operation on synchronous refresh group string failed unexpectedly.
Cause: The lock operation on the specified synchronous refresh group failed unexpectedly. This is an internal error.
Action: Contact Oracle Support Services for assistance.
QSM-03255: The unlock operation on synchronous refresh group string failed unexpectedly.
Cause: The unlock operation on the specified synchronous refresh group failed unexpectedly. This is an internal error.
Action: Contact Oracle Support Services for assistance.
QSM-03256: The synchronous refresh group string is locked by another operation.
Cause: Either REGISTER_MVIEWS or PREPARE_REFRESH detected that the synchronous refresh group to be processed by the requested operation had been locked by another synchronous refresh operation.
Action: Wait for the other operation to complete before attempting this operation again.
QSM-03257: The synchronous refresh group string has been unlocked by another operation.
Cause: Either EXECUTE_REFRESH or ABORT_REFRESH detected that the synchronous refresh group to be processed by the requested operation had been unlocked by another synchronous refresh operation. This is an unexpected condition and may indicate an internal error.
Action: Contact Oracle Support Services for assistance.
QSM-03258: The value supplied for the parameter string is too long.
Cause: The value supplied for the specified parameter exceeded the maximum length allowed for that parameter.
Action: Supply a valid value for the specified parameter.
QSM-03259: The value supplied for the parameter string is malformed.
Cause: The value supplied for the specified parameter was invalid.
Action: Supply a valid value for the specified parameter.
QSM-03260: The materialized views being registered are not defined on tables.
Cause: The materialized views being registered were not defined on tables, but were defined on top of other types of objects such as views or materialized views. Synchronous refresh works only with materialized views defined on tables.
Action: Do not register such materialized views for synchronous refresh.
QSM-03261: The partition operation name string is not valid.
Cause: Either REGISTER_PARTITION_OPERATION or UNREGISTER_PARTITION_OPERATION detected that the partition operation name did not belong to the DROP, EXCHANGE or TRUNCATE value.
Action: Check the parameter partition operation carefully, and change it to DROP, EXCHANGE or TRUNCATE.
QSM-03262: The object string.string is not registered for Synchronous Refresh.
Cause: REGISTER_PARTITION_OPERATION or UNREGISTER_PARTITION_OPERATION detected that either:

- This object was not registered for synchronous refresh.

- The synchronous refresh group was not in the current run.

- The object was not a table type.

Action: Make sure this object is registered for synchronous refresh, the synchronous refresh group is in the current run, and the object is a table type.
QSM-03263: There is already a partition operation registered on string.string partition string.
Cause: REGISTER_PARTITION_OPERATION detected that there was already a partition maintenance operation (for example, DROP, EXCHANGE or TRUNCATE) registered on the specified partition of the base table.
Action: Use the UNREGISTER_PARTITION_OPERATION to unregister this partition first, and then run REGISTER_PARTITION_OPERATION.
QSM-03264: There is no partition named string in base table string.string.
Cause: REGISTER_PARTITION_OPERATION detected that there was no partition with the specified name in the base table.
Action: Check the parameter PARTITION_NAME, and make sure it is a valid partition in the base table.
QSM-03265: The outside table string.string does not exist.
Cause: REGISTER_PARTITION_OPERATION detected that the outside table schema or table name did not exist or was not valid.
Action: Check the parameters OUTSIDE_PARTN_TABLE_SCHEMA or OUTSIDE_PARTN_TABLE_NAME, and make sure the outside table exists.
QSM-03266: Tablespace of base table string does not match the tablespace of outside partition table string.
Cause: REGISTER_PARTITION_OPERATION detected that the tablespace of the base table for any partition or subpartition did not match the tablespace of the outside partition table.
Action: Alter the tablespace of outside partition table to match the tablespace of the base table, or check if the outside partition table is eligible for REGISTER_PARTITION_OPERATION or not.
QSM-03267: The outside partition table string contains at least one record that is not within the partition range of the base table string.
Cause: REGISTER_PARTITION_OPERATION detected that the outside partition table contained at least one record that was not within the partition range of the base table.
Action: Check the records to see if the outside partition table is eligible for the REGISTER_PARTITION_OPERATION.
QSM-03268: Synchronous refresh can only support top partition by RANGE.
Cause: REGISTER_PARTITION_OPERATION detected the base table was not partitioned by RANGE on top.
Action: The base table is not eligible for REGISTER_PARTITION_OPERATION.
QSM-03269: The number of partitions of the base table string and the outside table string do not match.
Cause: The base table was composite-partitioned. The partition number of the outside partition did not match the number of subpartitions inside the specified partition of the base table.
Action: Check the partitions to see if the outside partition table is eligible for the REGISTER_PARTITION_OPERATION.
QSM-03270: There is no partition operation registered on string.string partition string.
Cause: UNREGISTER_PARTITION_OPERATION detected that there was no partition maintenance operation (for example, DROP, EXCHANGE and TRUNCATE) registered on the specified partition of the base table.
Action: Use the REGISTER_PARTITION_OPERATION to register this partition first, and then run UNREGISTER_PARTITION_OPERATION.
QSM-03271: The partition name of outside partition table string does not match the subpartition name of base table string.
Cause: REGISTER_PARTITION_OPERATION detected that the partition name of the outside partition table did not match the subpartition name of base table.
Action: Alter the partition name of outside partition table to match the partition name of the base table, or check if the outside partition table is eligible for REGISTER_PARTITION_OPERATION or not.
QSM-03272: There are no changes loaded for any tables in this group.
Cause: There were no changes recorded for any tables in this group. The changes to a table can be provided in its staging log or by specifying partition change operations with REGISTER_PARTITION_OPERATION.
Action: Provide the appropriate changes to the tables in the group.
QSM-03276: The specified schema string of the staging log is different from the owning schema string of the base table.
Cause: The user-specified schema of the staging log was different from the owning schema of the base table. They must be in the same schema if the schema of the staging log is specified.
Action: Specify the owning schema of the base table as the schema of the staging log or do not specify the schema for the staging log.
QSM-03277: An internal error related to tracing messages to SYNCREF_MESG has occurred.
Cause: This is an internal error as noted in the message.
Action: Contact Oracle Support Services for assistance.
QSM-03278: The table SYNCREF_MESG is not present in the SYS schema.
Cause: This is an internal error related to tracing messages to the table SYNCREF_MESG. It occurs if the event 31904 is set to level 4 or 8 but the message table SYNCREF_MESG is not created in the SYS schema. Oracle does not support levels 4 and 8 in event 31904.
Action: Execute the command again after unsetting levels 4 and 8 in event 31904.
QSM-03280: One or more materialized views failed to refresh successfully.
Cause: The base tables in the group refreshed successfully but one or more materialized views in the group did not. The status of the group for synchronous refresh operation was set to PARTIAL in this case.
Action: To find the materialized views which failed, query the USER_SR_OBJ_STATUS catalog view. Take one of the following courses of action:

* Issue the EXECUTE_REFRESH command again to retry refreshing the views. In this case EXECUTE_REFRESH will internally use the PCT refresh mode to refresh the materialized views.

* Issue the ABORT_REFRESH command to abort the refresh of all objects in the group, including the base tables, and restore them to the original state.

QSM-03281: The specified GROUP_ID is not valid.
Cause: The GROUP_ID specified as input to the refresh operation was not valid and does not identify a valid synchronous refresh group.
Action: Provide the correct GROUP_ID. Use the DBMS_SYNC_REFRESH.GET_GROUP_ID to get the correct GROUP_ID.
QSM-03282: A materialized view is registered on a table related to string.string.
Cause: The staging log creation on the specified table failed because a table related to it by referential-integrity constraint has a materialized view which was registered for synchronous refresh with the REGISTER_MVIEWS command. Oracle requires that you first register the tables before registering any materialized view defined on them.
Action: Unregister the materialized views defined on the related tables with the UNREGISTER_MVIEWS command. Then, register the tables with synchronous refresh by creating staging logs on them. Finally, register any materialized views you wish to register for synchronous refresh with REGISTER_MVIEWS.
QSM-03283: The materialized view string.string has not been registered.
Cause: The specified materialized view was not registered for synchronous refresh.
Action: Register the materialized view with DBMS_SYNC_REFRESH.REGISTER_MVIEWS. Use the USER_SR_OBJ catalog view to verify the materialized view has been registered.
QSM-03284: There is no foreign key constraint defined on string referencing string.string.
Cause: The table of REGISTER_PARTITION_OPERATION did not define a foreign key constraint on its referred base table.
Action: Define a foreign key constraint on its referred base table and retry the operation.
QSM-03285: There is no primary key constraint defined on string.string.
Cause: The table of REGISTER_PARTITION_OPERATION did not define a primary key constraint on it.
Action: Define a primary key constraint on the table and retry the operation.
QSM-03286: Complex materialized view was not allowed for synchronous refresh.
Cause: There was a complex materialized view in the synchronous refresh group.
Action: Remove the complex materialized view in the synchronous refresh group.
QSM-03287: synchronous refresh internal error: [string]
Cause: This was an internal error in synchronous refresh.
Action: Contact Oracle Support Services with the complete message.