ORA-26752: Unsupported LCR received for "string"."string"

Cause : Streams capture process received an LCR with unsupported operation from LogMiner.

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

If this object is listed in DBA_STREAMS_UNSUPPORTED view, modify rules to prevent changes made to this object from getting captured.

update : 23-06-2017

ORA-26752 - Unsupported LCR received for "string"."string"
ORA-26752 - Unsupported LCR received for "string"."string"

  • ora-19559 : error sending device command: string
  • ora-30012 : undo tablespace 'string' does not exist or of wrong type
  • ora-36952 : (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option.
  • ora-29395 : cannot set the initial consumer group to string
  • ora-29365 : parameters string and string cannot both be set
  • ora-28004 : invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string
  • ora-10997 : another startup/shutdown operation of this instance inprogress
  • ora-39003 : unable to get count of total workers alive
  • ora-02429 : cannot drop index used for enforcement of unique/primary key
  • ora-36628 : (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.
  • ora-31650 : timeout waiting for master process response
  • ora-01527 : error while reading file
  • ora-22344 : can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change
  • ora-16559 : out of memory at string
  • ora-23325 : parameter type is not string
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-25201 : invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
  • ora-01035 : ORACLE only available to users with RESTRICTED SESSION privilege
  • ora-09717 : osnsui: maximum number of user interrupt handlers exceeded.
  • ora-27214 : skgfrsfe: file search failed
  • ora-27007 : failed to open file
  • ora-18010 : command missing mandatory CATEGORY keyword
  • ora-12168 : TNS:Unable to contact LDAP Directory Server
  • ora-23533 : object "string"."string" can not be cached
  • ora-08454 : more than one S symbol specified in picture mask
  • ora-01218 : logfile member is not from the same point-in-time
  • ora-28606 : block too fragmented to build bitmap index (string,string)
  • ora-32343 : let MVIEW engine know that it is IMPORT from 9i or earlier
  • ora-16013 : log string sequence# string does not need archiving
  • ora-19251 : XQ0031 - unsupported query version
  • 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.