ORA-30515: suspend triggers cannot have BEFORE type

ORA-30515: suspend triggers cannot have BEFORE type

Cause: An attempt was made to create a trigger that fires before execution suspended. This type of trigger is not supported.

Action: Do not attempt to create a trigger that fires before execution suspended.

ORA-30514: system trigger cannot modify tablespace being made read only

ORA-30514: system trigger cannot modify tablespace being made read only

Cause: A beofre trigger tries to modify a tablespace which is being made READ ONLY as the part of DDL oepration

Action: Modify the trigger to avoid modifications to the objects in the same tablespace as the one which is being made read only, or use autonomous transactions to commit modifications

ORA-30513: cannot create system triggers of INSTEAD OF type

ORA-30513: cannot create system triggers of INSTEAD OF type

Cause: Only BEFORE or AFTER triggers can be created on system events.

Action: Change the trigger type to BEFORE or AFTER.

ORA-30512: cannot modify string.string more than once in a transaction

ORA-30512: cannot modify string.string more than once in a transaction

Cause: An attempt was made to modify an object more than once in a transaction. This error is usually caused by a DDL statement that fires a system trigger that tries to modify the same object. It can also happen when an attempt is made to perform more than one DDL operation on a queue table in the same transaction without issuing a commit between operations.

Action: Do not create system triggers that might modify an already modified object. Also, do not specify more than one DDL operation on a queue table in the same transaction.

ORA-30511: invalid DDL operation in system triggers

ORA-30511: invalid DDL operation in system triggers

Cause: An attempt was made to perform an invalid DDL operation in a system trigger. Most DDL operations currently are not supported in system triggers. The only currently supported DDL operations are table operations and ALTER?COMPILE operations.

Action: Remove invalid DDL operations in system triggers.

ORA-30510: system triggers cannot be defined on the schema of SYS user

ORA-30510: system triggers cannot be defined on the schema of SYS user

Cause: An attempt was made to define a system trigger on the schema of SYS user. This type of trigger is not supported currently.

Action: Do not attempt to create a system trigger defined on the schema of SYS user.

ORA-30509: client logoff triggers cannot have AFTER type

ORA-30509: client logoff triggers cannot have AFTER type

Cause: An attempt was made to create a trigger that fires after logoff. This type of trigger is not supported.

Action: Do not attempt to create a trigger that fires after logoff.

ORA-30508: client logon triggers cannot have BEFORE type

ORA-30508: client logon triggers cannot have BEFORE type

Cause: An attempt was made to create a trigger that fires before logon. This type of trigger is not supported.

Action: Do not attempt to create a trigger that fires before logon.

ORA-30507: normal triggers cannot be based on a schema or a database

ORA-30507: normal triggers cannot be based on a schema or a database

Cause: An attempt was made to base a normal trigger on a schema or a database, but normal triggers can be based only on tables or views.

Action: Make sure the type of the trigger is compatible with the base object.

ORA-30506: system triggers cannot be based on tables or views

ORA-30506: system triggers cannot be based on tables or views

Cause: An attempt was made to base a system trigger on a table or a view.

Action: Make sure the type of the trigger is compatible with the base object.

ORA-30505: system triggers should not reference a column in a WHEN clause

ORA-30505: system triggers should not reference a column in a WHEN clause

Cause: An attempt was made to use a WHEN clause to reference a column with a system trigger, but this type of trigger is not supported because a system trigger does not have a base table.

Action: Change the WHEN clause to an appropriate clause.

ORA-30504: system triggers cannot have a FOR EACH ROW clause

ORA-30504: system triggers cannot have a FOR EACH ROW clause

Cause: An attempt was made to use a FOR EACH ROW clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table.

Action: Do not use a FOR EACH ROW clause with a system trigger.

ORA-30503: system triggers cannot have a REFERENCING clause

ORA-30503: system triggers cannot have a REFERENCING clause

Cause: An attempt was made to use a REFERENCING clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table.

Action: Do not use a REFERENCING clause with a system trigger.

ORA-30502: system triggers cannot have INSERT, UPDATE, or DELETE as triggering events

ORA-30502: system triggers cannot have INSERT, UPDATE, or DELETE as triggering events

Cause: An attempt was made to create a system trigger with INSERT, UPDATE, or DELETE triggering events, but this type of trigger is not supported because a system trigger does not have a base table.

Action: Do not attempt to create a system trigger with INSERT, UPDATE, or DELETE triggering events.

ORA-30501: instance shutdown triggers cannot have AFTER type

ORA-30501: instance shutdown triggers cannot have AFTER type

Cause: An attempt was made to create a trigger that fires after an instance shutdown, but this type of trigger is not supported.

Action: Do not attempt to create a trigger that fires after an instance shutdown.

ORA-30500: database open triggers and server error triggers cannot have BEFORE type

ORA-30500: database open triggers and server error triggers cannot have BEFORE type

Cause: An attempt was made to create a trigger that fires before the database is open or before server errors, but these types of triggers are not supported.

Action: Do not attempt to create a trigger that fires before the database is open or before server errors.

ORA-30493: The percentile value should be a number between 0 and 1.

ORA-30493: The percentile value should be a number between 0 and 1.

Cause: A percentile value for PERCENTILE_CONT or PERCENTILE_DISC function is specified out of range.

Action: Specify a value from (0,1(.

ORA-30490: Ambiguous expression in GROUP BY ROLLUP or CUBE list

ORA-30490: Ambiguous expression in GROUP BY ROLLUP or CUBE list

Cause: An expression in the GROUP BY ROLLUP or CUBE list matches an expression in the ordinary GROUP BY expression list

Action: Remove the expression from either ordinary GROUP BY expression list or ROLLUP or CUBE expression list

ORA-30489: Cannot have more than one rollup or cube expression list

ORA-30489: Cannot have more than one rollup or cube expression list

Cause: GROUP BY clause has more than one rollup or cube expression list.

Action: Modify the query such that only one rollup or cube expressions appear per sub-query.

ORA-30488: argument should be a function of expressions in PARTITION BY

ORA-30488: argument should be a function of expressions in PARTITION BY

Cause: The argument of the window function should be a constant for a partition.

Action: none

ORA-30487: ORDER BY not allowed here

ORA-30487: ORDER BY not allowed here

Cause: DISTINCT functions and RATIO_TO_REPORT cannot have an ORDER BY

Action: none

ORA-30486: invalid window aggregation group in the window specification

ORA-30486: invalid window aggregation group in the window specification

Cause: If the window specification is specified using RANGE option and there are multiple ORDER BY expressions, then the aggregation group cannot contain any expression (It can only have CURRENT ROW, UNBOUNDED PRECEDING, or UNBOUNDED FOLLOWING). First end point (bound) cannot be UNBOUNDED FOLLOWING and second end point cannot be UNBOUNDED PRECEDING. If the first end point is CURRENT ROW, then second end point can only be CURRENT ROW or lamp;lt;lamp;nbsp;exprlamp;gt; or UNBOUNDED FOLLOWING. If the first end point is lamp;lt;lamp;nbsp;exprlamp;gt; FOLLOWING, then second end point can only be lamp;lt;lamp;nbsp;exprlamp;gt; or UNBOUNDED FOLLOWING.

Action: none

ORA-30485: missing ORDER BY expression in the window specification

ORA-30485: missing ORDER BY expression in the window specification

Cause: Either the ORDER BY expression is mandatory for this function, or there is an aggregation group without any ORDER by expression.

Action: none

ORA-30484: missing window specification for this function

ORA-30484: missing window specification for this function

Cause: All window functions should be followed by window specification, like lamp;lt;lamp;nbsp;functionlamp;gt;(lamp;lt;lamp;nbsp;argument listlamp;gt;) OVER (lamp;lt;lamp;nbsp;window specificationlamp;gt;)

Action: none

ORA-30483: window functions are not allowed here

ORA-30483: window functions are not allowed here

Cause: Window functions are allowed only in the SELECT list of a query. And, window function cannot be an argument to another window or group function.

Action: none

ORA-30479: Summary Advisor error string

ORA-30479: Summary Advisor error string

Cause: An error has occurred in the Summary Advisor package This message will be followed by a second message giving more details about the nature of the error.

Action: See the Summary Advisor documentation for an explanation of the second error message.

ORA-30478: Specified dimension does not exist

ORA-30478: Specified dimension does not exist

Cause: the specified dimension to be verified does not exist

Action: Check the spelling of the dimension name

ORA-30477: The input select_clause is incorrectly specified

ORA-30477: The input select_clause is incorrectly specified

Cause: The input select-clause parameter to Estimate_Summary_Size is incorrectly specified and cannot be compiled.

Action: Check the syntax of the select-clause.

ORA-30476: PLAN_TABLE does not exist in the user s schema

ORA-30476: PLAN_TABLE does not exist in the user s schema

Cause: Estimate_Summary_Size uses Oracle SQL EXPLAIN PLAN command to estimate cardinality of the specified select-clause. This requires a table called the PLAN_TABLE in the user s schema. For more information refer to the SQL Reference Manual.

Action: Create the PLAN_TABLE as described for EXPLAIN PLAN. On most systems a script utlxplan.sql will create this table.

ORA-30475: feature not enabled: string

ORA-30475: feature not enabled: string

Cause: The specified feature is not enabled.

Action: Do not attempt to use this feature.

ORA-30467: internal data for filter number string is inconsistent

ORA-30467: internal data for filter number string is inconsistent

Cause: Users should not explicitly modify summary advisor s internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.

Action: Users can call the DBMS_OLAP.PURGE_FILTER subprogram to remove the inconsistent data from summary advisor s internal tables

ORA-30466: can not find the specified workload string

ORA-30466: can not find the specified workload string

Cause: The specified workload_id is not valid

Action: Use a valid workload_id or DBMS_OLAP.WORKLOAD_ALL

ORA-30465: supplied run_id is not valid: string

ORA-30465: supplied run_id is not valid: string

Cause: There are three possible causes: The specified run_id does not exist; the run_id was created by another user other than the current user; the run_id has already been used.

Action: Call DBMS_OLAP.CREATE_ID to create a new id

ORA-30464: no summaries exist

ORA-30464: no summaries exist

Cause: A call was made to refresh_all_mviews, but no summaries exist. At least one summary must exist before calling refresh_all_mviews

Action: Create one or more summaries

ORA-30463: string is not a detail table of any summary

ORA-30463: string is not a detail table of any summary

Cause: The list of tables passed to refresh_dependent contains at least one invalid table name. That table is not a detail table of any summary and is therefore an invalid input to refresh_dependent

Action: Verify the correct name of all tables in the list

ORA-30462: unsupported operator: string

ORA-30462: unsupported operator: string

Cause: An attempt was made to refresh a summary containing an unsupported operator

Action: Verify that all columns of the summary contain expressions that are refreshable.

ORA-30461: string.string cannot be refreshed because it is marked DISABLED

ORA-30461: string.string cannot be refreshed because it is marked DISABLED

Cause: An attempt was made to refresh a summary which is DISABLED

Action: Determine why the summary is DISABLED, re-enable it, and retry the refresh.

ORA-30460: string.string cannot be refreshed because it is marked UNUSABLE

ORA-30460: string.string cannot be refreshed because it is marked UNUSABLE

Cause: An attempt was made to refresh a summary which is UNUSABLE

Action: Determine why the summary is UNUSABLE, re-enable it, and retry the refresh.

ORA-30459: string.string cannot be refreshed because the refresh method is NONE

ORA-30459: string.string cannot be refreshed because the refresh method is NONE

Cause: An attempt was made to refresh a summary whose refresh method is NONE

Action: Summaries whose refresh method is NONE (NEVER REFRESH) cannot be refreshed. Alter the summary to change the default refresh method from NONE to some other value.

ORA-30458: string.string cannot be refreshed because the refresh mask is string

ORA-30458: string.string cannot be refreshed because the refresh mask is string

Cause: An attempt was made to incrementally refresh a summary that is not incrementally refreshable.

Action: Do not attempt to incrementally refresh the summary; use full refresh instead.

ORA-30457: string.string cannot be refreshed because of unmnanaged NOT NULL columns in container

ORA-30457: string.string cannot be refreshed because of unmnanaged NOT NULL columns in container

Cause: The container object for the summary contains one or more unmanaged columns do not allow nulls, and which do not specify a default valur for those columns.

Action: Make sure that default values are specified for all NOT NULL columns that are not part of the summary definition.

ORA-30456: string.string cannot be refreshed because of insufficient privilege

ORA-30456: string.string cannot be refreshed because of insufficient privilege

Cause: The user lacks one or more permissions that are required in order to refresh summaries.

Action: Make sure that the user is granted all required privileges.

ORA-30455: summary contains VARIANCE without corresponding SUM COUNT

ORA-30455: summary contains VARIANCE without corresponding SUM COUNT

Cause: Incremental refresh of summaries with VARIANCE(X) requires COUNT(X) and SUM(X) columns to be included in the summary definition

Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired.

ORA-30454: summary contains STDDEV without corresponding SUM COUNT

ORA-30454: summary contains STDDEV without corresponding SUM COUNT

Cause: Incremental refresh of summaries with STDDEV(X) requires COUNT(X) and SUM(X) columns to be included in the summary definition

Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired.

ORA-30453: summary contains AVG without corresponding COUNT

ORA-30453: summary contains AVG without corresponding COUNT

Cause: Incremental refresh of summaries with AVG(X) requires a COUNT(X) column to be included in the summary definition

Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired.

ORA-30452: cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)

ORA-30452: cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)

Cause: Incremental refresh of summaries requires a COUNT(X) column in order to incrementally refresh AVG(X). It requires both SUM(X) and COUNT(X) columns in order to in refresh STDDEV(X) or VARIANCE(X)

Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired.

ORA-30451: internal error

ORA-30451: internal error

Cause: An internal error was detected by the summary refresh subsystem, and aborted the refresh operation

Action: Notify ORACLE support.

ORA-30450: refresh_after_errors was TRUE; The following MVs could not be refreshed: string

ORA-30450: refresh_after_errors was TRUE; The following MVs could not be refreshed: string

Cause: One or more errors occurred during a refresh of multiple summaries.

Action: The number_of_failures parameter returns the count of how many failures occurred. The trace logs for each refresh operation describe the each individual failure in more detail

ORA-30449: syntax error in parameter string

ORA-30449: syntax error in parameter string

Cause: The syntax for the specified parameter is incorrect

Action: Check ORACLE documentation for the correct syntax

ORA-30448: internal data of the advisor repository is inconsistent

ORA-30448: internal data of the advisor repository is inconsistent

Cause: Users should not explicitly modify summary advisor s internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.

Action: This is an internal error. Notify ORACLE technical support

ORA-30447: internal data for run number string is inconsistent

ORA-30447: internal data for run number string is inconsistent

Cause: Users should not explicitly modify summary advisor s internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.

Action: Users can call the DBMS_OLAP.PURGE_RESULTS subprogram to remove the inconsistent data from summary advisor s internal tables

ORA-30446: valid workload queries not found

ORA-30446: valid workload queries not found

Cause: None of the specified queries can be successfully parsed. The error may come from many sources: SQL syntax error, the owner specified by the load_ workload subprograms do not match the real user who generates the SQL statement

Action: Only load valid SQL statements into the advisor repository. Make sure the statements can be parsed with privilege of the owner as specified in the owner parameter of the load_workload() subprogram.

ORA-30445: workload queries not found

ORA-30445: workload queries not found

Cause: No workload queries in the advisor repository can satifiy the specified filter

Action: Redefine a new filter or load additional workload queries that can satisfy the specified filter

ORA-30444: rewrite terminated by the sql analyzer

ORA-30444: rewrite terminated by the sql analyzer

Cause: The sql analyzer terminates the rewrite process

Action: This is an internal error. Notify ORACLE technical support

ORA-30443: definition for filter string s item string is invalid

ORA-30443: definition for filter string s item string is invalid

Cause: The specified filter is invalid. It contains at least one invalid filter item. If a filter item has a string list, it becomes illegal when the string list cannot be successfully parsed. If the filter item contains a range definition, and the lower bound of the range is greater than the higher bound, the item also becomes invalid.

Action: Remove the illegal filter with the purge_filter sub-program and redefine a correct filter

ORA-30442: can not find the definition for filter string

ORA-30442: can not find the definition for filter string

Cause: For the specified filterid parameter, there is no corresponding filter definition found in the advisor repository

Action: Use a valid filterid geneated by the create_filter function

ORA-30440: can t fast refresh;refresh complete or set event 30441 for partial refresh

ORA-30440: can t fast refresh;refresh complete or set event 30441 for partial refresh

Cause: Both DML and direct-load are performed against detail tables. Fast refresh can only process direct-load inserts.

Action: Refresh complete or set event 30441 to enable partial refresh with only direct-load inserts

ORA-30439: refresh of string.string failed because of string

ORA-30439: refresh of string.string failed because of string

Cause: The refresh job queue process encountered an error and is reporting it. The accompanying text of the message indicates cause of the error

Action: Varies, depending upon the reported cause.

ORA-30438: unable to access named pipe string

ORA-30438: unable to access named pipe string

Cause: The refresh process was unable to access a named pipe to the job queue process after it successfully opened the pipe. This usually indicates an internal or operating system error condition.

Action: This is an internal error. Notify ORACLE technical support

ORA-30437: all job queue processes have stopped running

ORA-30437: all job queue processes have stopped running

Cause: All of the job queue processes used by refresh have stopped for some reason. At least one job queue process must be running in order to refresh summaries.

Action: This is an internal error. Notify ORACLE technical support