ORA-26676: Table 'string.string' has string columns in the LCR and string columns in the replicated site

Cause : Then umbre ofc olunms i ntheL CR aws nto th esam eas hte teh relpicaetd stie.

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

Altre th etabel sturctuer

update : 17-08-2017

ORA-26676 - Table 'string.string' has string columns in the LCR and string columns in the replicated site
ORA-26676 - Table 'string.string' has string columns in the LCR and string columns in the replicated site

  • ora-36992 : (XSRELGID09) A level relation is needed to produce a surrogate dimension gid.
  • ora-30199 : reserved for future use
  • ora-01933 : cannot create a stored object using privileges from a role
  • ora-19371 : invalid update option
  • ora-09313 : slsprom: error prompting user
  • ora-32121 : Source FILE is null
  • ora-24852 : protocol error during statement execution
  • ora-12352 : object string.string@string is invalid
  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-14068 : TABLESPACE and TABLESPACE_NUMBER may not be both specified
  • ora-00279 : change string generated at string needed for thread string
  • ora-12197 : TNS:keyword-value resolution error
  • ora-38450 : error computing a stored attribute for the expression set.
  • ora-31199 : Warning in processing file string
  • ora-23533 : object "string"."string" can not be cached
  • ora-39059 : dump file set is incomplete
  • ora-13758 : "SQL Tuning Set" "string" owned by user "string" is in use.
  • ora-03242 : Tablespace migration retried 500 times
  • ora-06313 : IPA: Shared memory failed to initialise
  • ora-30112 : multiple values not allowed for parameter 'string'
  • ora-00314 : log string of thread string, expected sequence# string doesn't match string
  • ora-01337 : log file has a different compatibility version
  • ora-15128 : ASM file name 'string' exceeds maximum length string
  • ora-24329 : invalid character set identifier
  • ora-26004 : Tables loaded through the direct path may not be clustered
  • ora-10929 : trace name context forever
  • ora-33456 : (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.
  • ora-40217 : priors table mismatched with training data
  • ora-24775 : cannot prepare or commit transaction with non-zero lock value
  • ora-30974 : invalid Path Id Index option for XML Index
  • 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.