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 : 29-04-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-01916 : keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected
  • ora-28593 : agent control utility: command terminated with error
  • ora-01270 : %s operation is not allowed if STANDBY_PRESERVES_NAMES is true
  • ora-15109 : conflicting protection attributes specified
  • ora-32156 : Cannot perform operation on stream
  • ora-31497 : invalid value specified for first_scn
  • ora-39019 : invalid operation type string
  • ora-12993 : tablespace 'string' is offline, cannot drop column
  • ora-36630 : (XSDUNION00) An empty base dimension list was specified in the concat dimension definition.
  • ora-10664 : Table has bitmap join indexes
  • ora-28001 : the password has expired
  • ora-08113 : composite partition index may not be compressed
  • ora-12158 : TNS:could not initialize parameter subsystem
  • ora-29540 : class string does not exist
  • ora-32800 : internal error string
  • ora-13029 : Invalid SRID in the SDO_GEOMETRY object
  • ora-07392 : sftcls: fclose error, unable to close text file.
  • ora-13347 : the coordinates defining an arc are not distinct
  • ora-24085 : operation failed, queue string is invalid
  • ora-07635 : smsdbp: $SETPRT failure
  • ora-02773 : Invalid maximum client wait time
  • ora-09817 : Write to audit file failed.
  • ora-32143 : Environment not specified
  • ora-37011 : (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
  • ora-13783 : invalid tuning scope
  • ora-31693 : Table data object string failed to load/unload and is being skipped due to error: string
  • ora-14095 : ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table
  • ora-01941 : SEQUENCE keyword expected
  • ora-02074 : cannot string in a distributed transaction
  • ora-30184 : argument type not compatible with a format code
  • 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.