ORA-32588: supplemental logging attribute string exists

ORA-32588: supplemental logging attribute string exists

Cause: specified supplemental logging attribute exits.

Action: retry the alter or create ddl after removing this supplemental logging attribute.

ORA-32587: Cannot drop nonexistent string supplemental logging

ORA-32587: Cannot drop nonexistent string supplemental logging

Cause: specified supplemental log attribute does not exist.

Action: None

ORA-32586: multiple specification of a supplemental logging attribute

ORA-32586: multiple specification of a supplemental logging attribute

Cause: The primary key, unique index, foreign key or all column supplemental logging attribute can be specified at most once in a create or alter ddl.

Action: Rewrite the Create or Alter DDL with single occurence of the offending supplemental logging attribute.

ORA-32585: duplicate specification of a supplemental log attribute

ORA-32585: duplicate specification of a supplemental log attribute

Cause: In a create or alter DDL a supplemental log attribute is specified more than once.

Action: Rewrite the Create or Alter DDL such that it has a single occurence of any supplemental log attribute.

ORA-32584: missing LOG keyword

ORA-32584: missing LOG keyword

Cause: keyword LOG is missing.

Action: Use LOG keyword.

ORA-32583: query passed to table function has wrong number of elements in select list

ORA-32583: query passed to table function has wrong number of elements in select list

Cause: The query used as an input to a table function which takes a a ref cursor as argument has wrong number of elements in the select list which does not correspond to the elements in ref cursor. The ref cursor mentioned here refers to the one referenced in order by parition clauses. This is not allowed.

Action: Make sure that the select list of the query matches the ref cursor columns as defined in the function.

ORA-32582: table function with left correlation to a table cannot also be left outer-joined to the table

ORA-32582: table function with left correlation to a table cannot also be left outer-joined to the table

Cause: A table function T2 contains a reference to a table T1. T2 is also left outer-joined to T1. This is not allowed.

Action: Remove the reference to T1 from T2 or remove the left outer-join specification (+).

ORA-32581: missing or invalid password

ORA-32581: missing or invalid password

Cause: An incorrect password was provided for the SYS or SYSTEM user in the CREATE DATABASE statement.

Action: Re-issue the CREATE DATABASE statement with a valid password.

ORA-32580: both SYS and SYSTEM passwords must be provided

ORA-32580: both SYS and SYSTEM passwords must be provided

Cause: Passwords for both the SYS and SYSTEM users were not provided in the CREATE DATABASE statement. If one of the passwords was provided, then both should be provided.

Action: Re-issue the CREATE DATABASE statement with a password for both the SYS and SYSTEM users.

ORA-32579: password for SYSTEM already specified

ORA-32579: password for SYSTEM already specified

Cause: A password for the SYSTEM user was specified twice in the CREATE DATABASE statement.

Action: Re-issue the CREATE DATABASE statement with only one password for the SYSTEM user.

ORA-32578: password for SYS already specified

ORA-32578: password for SYS already specified

Cause: A password for the SYS user was specified twice in the CREATE DATABASE statement.

Action: Re-issue the CREATE DATABASE statement with only one password for the SYS user.

ORA-32577: username must be SYS or SYSTEM

ORA-32577: username must be SYS or SYSTEM

Cause: A user name of SYS or SYSTEM was not specified when providing a password in the CREATE DATABASE statement.

Action: Only passwords for the SYS and SYSTEM users can be provided in the CREATE DATABASE statement. Re-issue the statement with passwords for users SYS or SYSTEM.

ORA-32576: missing TYPE keyword

ORA-32576: missing TYPE keyword

Cause: keyword TYPE is missing.

Action: Use TYPE keyword.

ORA-32575: Explicit column default is not supported for modifying views

ORA-32575: Explicit column default is not supported for modifying views

Cause: Default keyword was used to modify views.

Action: Use implicit default - omitting column-value pair.

ORA-32550: Replacement occured despite hint to the contrary

ORA-32550: Replacement occured despite hint to the contrary

Cause: This should never be signalled; it s internal.

Action: Report to Oracle support.

ORA-32518: cannot wait for ORADEBUG command completion (waited number ms for process string); total wait time exceeds number ms

ORA-32518: cannot wait for ORADEBUG command completion (waited number ms for process string); total wait time exceeds number ms

Cause: The total wait time for all targeted processes exceeded the maximum wait time, therefore the wait for the targeted process to finish executing the ORADEBUG command was aborted.

Action: Increase the timeout value.

ORA-32517: cannot issue ORADEBUG command (waited number ms for process string); total wait time exceeds number ms

ORA-32517: cannot issue ORADEBUG command (waited number ms for process string); total wait time exceeds number ms

Cause: The process targeted to execute the ORADEBUG command was busy executing another ORADEBUG command. But, because the total wait time for all targeted processes exceeded the maximum wait time, the ORADEBUG command was not issued to the target process.

Action: Increase the timeout value.

ORA-32516: cannot wait for ORADEBUG command completion; waited number ms for process string

ORA-32516: cannot wait for ORADEBUG command completion; waited number ms for process string

Cause: The execution of the ORADEBUG command took longer than the the timeout value specified.

Action: Increase the timeout value.

ORA-32515: cannot issue ORADEBUG command; waited number ms for process string

ORA-32515: cannot issue ORADEBUG command; waited number ms for process string

Cause: The process targeted to execute the ORADEBUG command was busy executing another ORADEBUG command for a time greater than the timeout value specified.

Action: Increase the timeout value.

ORA-32514: cannot dump multiple string types: structure size is unknown

ORA-32514: cannot dump multiple string types: structure size is unknown

Cause: trying to dump an invalid address

Action: provide a different valid address

ORA-32512: type string is unknown

ORA-32512: type string is unknown

Cause: trying to dump an invalid type name

Action: specify a known type

ORA-32511: cannot create watchpoint in memory needed by watchpointing code

ORA-32511: cannot create watchpoint in memory needed by watchpointing code

Cause: overlap exists between requested memory range to watch and internal memory structures that watchpointing operations need

Action: provide a different address range

ORA-32510: cannot create watchpoint on unreadable memory

ORA-32510: cannot create watchpoint on unreadable memory

Cause: trying to create watchpoint on invalid address

Action: provide a different valid address

ORA-32509: watchpoint was already deleted

ORA-32509: watchpoint was already deleted

Cause: trying to delete an already deleted watchpoint

Action: use oradebug show to list valid watchpoint ids

ORA-32508: no such watchpoint id

ORA-32508: no such watchpoint id

Cause: invalid watchpoint id

Action: use oradebug show to list valid watchpoint ids

ORA-32507: expecting string but found string

ORA-32507: expecting string but found string

Cause: invalid arguments to command

Action: provide one of the expected arguments

ORA-32506: expecting one of string, string, or string but found string

ORA-32506: expecting one of string, string, or string but found string

Cause: invalid arguments provided

Action: provide one of the expected arguments

ORA-32505: too many watchpoints

ORA-32505: too many watchpoints

Cause: too many watchpoints created

Action: increase appropriate initialization parameters

ORA-32504: expecting one of string, string, string, or string but found string

ORA-32504: expecting one of string, string, string, or string but found string

Cause: illegal value specified for create watchpoint mode

Action: specify one of the expected modes

ORA-32503: Mapping SGA from file failed

ORA-32503: Mapping SGA from file failed

Cause: Underlying OSDs encountered an error

Action: Check additional information. slercerrno contains errno.

ORA-32502: Cannot execute command. Flash Freeze is not in effect

ORA-32502: Cannot execute command. Flash Freeze is not in effect

Cause: This command can only be issued after a flash freeze

Action: Refer to instructions for flash freeze and Oracle diagnostics.

ORA-32501: Writing SGA to file failed

ORA-32501: Writing SGA to file failed

Cause: Underlying OSDs encountered an error

Action: Check additional information. slercerrno contains errno.

ORA-32500: Dirname string cannot exceed number characters

ORA-32500: Dirname string cannot exceed number characters

Cause: Path name too long

Action: Use shorter pathname than maximum specified for dirname.

ORA-32412: encrypted column string not allowed in the materialized view log

ORA-32412: encrypted column string not allowed in the materialized view log

Cause: The materialized view log being created or altered is to capture an encrypted column of the base table.

Action: Do not capture the encrypted column.

ORA-32411: materialized view definition query exceeds the maximum length

ORA-32411: materialized view definition query exceeds the maximum length

Cause: The materialized view definition query exceeds the 64K limit.

Action: Change the materialized view definition query so that it does not exceed the maximum length of 64K.

ORA-32409: materialized view log on string . string already excludes new values

ORA-32409: materialized view log on string . string already excludes new values

Cause: The materialized view log on the indicated table already excludes new values.

Action: No action required.

ORA-32408: materialized view log on string . string already has new values

ORA-32408: materialized view log on string . string already has new values

Cause: The materialized view log on the indicated table already has new values.

Action: No action required.

ORA-32407: cannot exclude new values when materialized view log includes new values

ORA-32407: cannot exclude new values when materialized view log includes new values

Cause: The excluding new values specification for the existing materialized view log cannot be accepted when including new values is the current option.

Action: change excluding new values clause.

ORA-32406: cannot alter partitioning for existing materialized view log

ORA-32406: cannot alter partitioning for existing materialized view log

Cause: The partitioning specification for the existing materialized view log cannot be altered or changed.

Action: remove the partitioning clause from the statement.

ORA-32405: cannot alter tablespace for existing materialized view log

ORA-32405: cannot alter tablespace for existing materialized view log

Cause: The tablespace specification for the existing materialized view log cannot be altered or changed.

Action: remove the tablespace clause from the statement.

ORA-32404: snapshot log uses Change Data Capture which is not enabled for this database

ORA-32404: snapshot log uses Change Data Capture which is not enabled for this database

Cause: A snapshot log that utilizes Change Data Capture is being imported to a database where Change Data Capture has not been enabled.

Action: First enable Change Data Capture on the database then retry the import.

ORA-32403: cannot use new values from mv log on string . string

ORA-32403: cannot use new values from mv log on string . string

Cause: The materialized view log either does not have new values logged, or the timestamp associated with the new values columns is more recent than the last refresh time.

Action: Perform a complete refresh is required before the next fast refresh.

ORA-32401: materialized view log on string . string does not have new values

ORA-32401: materialized view log on string . string does not have new values

Cause: Materialized view log on the indicated table does not have new values information.

Action: Add new values to materialized view log using the ALTER MATERIALIZED VIEW LOG command.

ORA-32400: cannot use object id columns from materialized view log on string. string

ORA-32400: cannot use object id columns from materialized view log on string. string

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.

ORA-32345: fail to refresh the materialized view string.string due to the changed synonym

ORA-32345: fail to refresh the materialized view string.string due to the changed synonym

Cause: The definition of one or more synonyms in the from clause have changed. The structure of the materialized view has become invalid.

Action: Restore the synonym(s) or drop the materialized view and recreate it again.

ORA-32344: cannot create a secondary materialized view with synonym as base table

ORA-32344: cannot create a secondary materialized view with synonym as base table

Cause: It is not supported to create a secondary materialized view with synonym in the FROM clause.

Action: Removed the synonym(s) from the statement.

ORA-32343: let MVIEW engine know that it is IMPORT from 9i or earlier

ORA-32343: let MVIEW engine know that it is IMPORT from 9i or earlier

Cause: N or A.

Action: Set this event only under the supervision of Oracle development. Not for general purpose use.

ORA-32342: The EXPLAIN_MVIEW facility failed to explain the materialized view statement

ORA-32342: The EXPLAIN_MVIEW facility failed to explain the materialized view statement

Cause: An error exists in the materialized view definition. As a result, the materialized view statement could not be explained.

Action: Check the syntax of the statement. If it is a CREATE MATERIALIZED VIEW statement, then also check the PARAMETERs specified for the materialized view.

ORA-32341: The EXPLAIN_MVIEW facility failed to explain the materialized view string. string

ORA-32341: The EXPLAIN_MVIEW facility failed to explain the materialized view string. string

Cause: The dependent object(s) of the materialized view may have changed. The materialized view may no longer be valid.

Action: Execute ALTER MATERIALIZED VIEW COMPILE and to determine the status of the materialized view in catalog views.

ORA-32340: cannot tune the materialized view definition

ORA-32340: cannot tune the materialized view definition

Cause: Due to constructs in the materialized view definition, it could not be tuned to be fast-refreshable or rewriteable.

Action: Execute DBMS_MVIEW.EXPLAIN_MVIEW to determine the cause.

ORA-32339: cannot alter materialized view with the PMOP

ORA-32339: cannot alter materialized view with the PMOP

Cause: the materialized view is not allowed to have destructive PMOPS such as DROP, TRUNCATE and EXCHANGE (sub)partition. The UGA flag of i_am_a_ refresh should be set first.

Action: execute set_i_am_a_refresh first before alter materialized view with the PMOP.

ORA-32338: on commit refresh grab all the detailed tables

ORA-32338: on commit refresh grab all the detailed tables

Cause: an event is set to let on-commit MV refresh to grab all the detailed tables, no matter whether they have modified or not.

Action: none

ORA-32337: cannot alter materialized view with pending changes refresh on commit

ORA-32337: cannot alter materialized view with pending changes refresh on commit

Cause: There are some pending changes in the detail tables

Action: Execute an on-demand refresh on the materialized view to synchronize the data between the materialized view and the detail tables and then issue an ALTER MATERIALIZED VIEW statement.

ORA-32336: cannot use USING NO INDEX to create materialized view string. string

ORA-32336: cannot use USING NO INDEX to create materialized view string. string

Cause: The USING NO INDEX option was specified to create an updatable primary key based materialized view, an index-organized materialized view or an object-id materialized view.

Action: Do not use the USING NO INDEX option to create an updatable primary key based materialized view, an index-organized materialized view or an object-id materialized view.

ORA-32335: dimension must have at least one level

ORA-32335: dimension must have at least one level

Cause: An level-less dimension is not allowed.

Action: Do not drop the only level of a dimension.

ORA-32334: cannot create prebuilt materialized view on a table already referenced by a MV

ORA-32334: cannot create prebuilt materialized view on a table already referenced by a MV

Cause: the table on which the materialized view is created as prebuilt is already referenced by a materialized view

Action: create the materialized view on a different table

ORA-32333: disable table scn update for Materialized view

ORA-32333: disable table scn update for Materialized view

Cause: an event is set for disabling table scn update to prevent deadlock situation. (bug 1376209)

Action: disable null refresh and or or base table scn update for Materialized view

ORA-32332: cannot refresh materialized view string . string as type evolution has occured

ORA-32332: cannot refresh materialized view string . string as type evolution has occured

Cause: The types used by the materialized view or its master tables have been evolved.

Action: Ensure that the types used by the materialized view have been evolved to the same version at both the master and materialized sites. Then, before refreshing the materialized view, evolve the materialized view using ALTER MATERIALIZED VIEW.

ORA-32331: type string . string is incompatible with the master site

ORA-32331: type string . string is incompatible with the master site

Cause: A type used by the materialized view was found to be incompatible with its coressponding type on the master site. This could be because the type does not exist on the master site or has been evolved to a different version from that on the materialzied view site.

Action: Make sure that the types used by the materialized view are the same on both the materialized view and master sites.

ORA-32330: invalid operation on online redefinition interim table string . string

ORA-32330: invalid operation on online redefinition interim table string . string

Cause: An invalid operation was performed on an interim table which was being used for online redefinition of a table.

Action: Do not perform any unsupported operation on the interim table.