ORA-23435: cannot create an updatable ROWID materialized view with LOB columns

Cause : The propagation of LOB data from materialized view sites to the master site requires a primary key on the replicated table. Thus updatable ROWID materialized views that contain LOB columns are not supported.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Create a primary key materialized view instead of a ROWID materialized view. If the materialized view already exists, it can be converted to a primary key materialized view using the ALTER MATERIALIZED VIEW DDL command.

update : 24-06-2017

ORA-23435 - cannot create an updatable ROWID materialized view with LOB columns
ORA-23435 - cannot create an updatable ROWID materialized view with LOB columns

  • ora-03236 : max # extents (string) reached in index string.string subpartition string
  • ora-26078 : file "string" is not part of database being loaded
  • ora-30990 : insufficient privileges to change owner of resource string
  • ora-36704 : (XSRELTBL06) workspace object should be dimensioned by workspace object.
  • ora-19527 : physical standby redo log must be renamed
  • ora-24184 : transformation string.string already exists
  • ora-30970 : option not supported for XML Index
  • ora-32304 : materialized views with user-defined types cannot use prebuilt table
  • ora-12722 : regular expression internal error
  • ora-28347 : encryption properties mismatch
  • ora-00062 : DML full-table lock cannot be acquired; DML_LOCKS is 0
  • ora-25005 : cannot CREATE INSTEAD OF trigger on a read-only view
  • ora-16004 : backup database requires recovery
  • ora-09855 : removeCallback: bad message format.
  • ora-32334 : cannot create prebuilt materialized view on a table already referenced by a MV
  • ora-02495 : cannot resize file string, tablespace string is read only
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-30401 : JOIN KEY columns must be non-null
  • ora-23408 : this replication operation is not supported in a mixed configuration
  • ora-30163 : The thread safety initialization failed
  • ora-06039 : NETDNT: connect failed
  • ora-39727 : COMPATIBLE must be set to or higher
  • ora-39753 : unsupported use of subquery in PARTITIONED OUTER JOIN condition
  • ora-27122 : unable to protect memory
  • ora-04087 : cannot change the value of ROWID reference variable
  • ora-01150 : cannot prevent writes - file string has online backup set
  • ora-30966 : error detected in the XML Index layer
  • ora-27508 : IPC error sending a message
  • ora-31398 : DBMS_LDAP: Shared servers are not supported.
  • ora-12341 : maximum number of open mounts exceeded
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.