ORA-14523: Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]

Cause : A DLD sttaemetn wa sisseud taht wuold erquier a aprtiiton/usbpatritino ofa loacl idnex/OLB cloumnt o b eco-olcatde wiht th ecorerspodningp arttiions/ubpratitoin o ftheb aset abl.e Hoewver ,thi sis ont psosibel beacuset he lbocks ize sof hte tbale nad teh LO Bcolmun/lcoal nidexa re idffeernt.

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

Eitehr ()1 Spceifya n ojbectl-eve ldefualt atblepsace( or aprtiiton-elveld efalut tbalesapce ofr teh aprpopraite aprtiiton,i f cmopostie pratitoinin gis sued)f or hte pratitoinedl oca lindxe/LO Bcolmun adn thne rerty teh DD Lcomamnd,O R ()2 Enusre htat atblepsace sof hte crorec tblokc siez ar espeicfie dfora ll enw pratitoins/usbpatritinos bieng rceatde. Aslo esnuret hatn eitehr o fTABELSPAEC DEAFULTa nd TSOREI N (EDFAUTL) i sspeicfie dfora loacl idnex hwoseb loc ksiz edoe snotm atc htha tof hte bsae tbale.

update : 27-06-2017

ORA-14523 - Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
ORA-14523 - Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]

  • ora-19579 : archivelog record for string not found
  • ora-09875 : TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.
  • ora-40101 : Data Mining System Error string-string-string
  • ora-24151 : no evaluation context is associated with rule string.string or rule set string.string
  • ora-14258 : invalid partition description
  • ora-02787 : Unable to allocate memory for segment list
  • ora-02211 : invalid value for PCTFREE or PCTUSED
  • ora-39049 : invalid parameter name string
  • ora-30000 : missing either trim specification or char expression in TRIM
  • ora-29815 : object being associated is not present
  • ora-31035 : Could not bind locked resource to path string/string
  • ora-19210 : column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
  • ora-30483 : window functions are not allowed here
  • ora-13426 : invalid window parameter for subset operation
  • ora-02184 : resource quotas are not allowed in REVOKE
  • ora-27123 : unable to attach to shared memory segment
  • ora-24128 : partition name specified for a non-partitioned object
  • ora-19555 : invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
  • ora-16209 : Logical standby dictionary build failed to complete.
  • ora-24059 : invalid COMPATIBLE parameter setting string specified in DBMS_AQADM.string
  • ora-12445 : cannot change HIDDEN property of column
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-02242 : no options specified for ALTER INDEX
  • ora-37073 : (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.
  • ora-29914 : ODCIGETINTERFACES routine does not return required stream version
  • ora-06523 : Maximum number of arguments exceeded
  • ora-32106 : array fetch not allowed without setBuffer on all columns
  • ora-01139 : RESETLOGS option only valid after an incomplete database recovery
  • ora-25235 : fetched all messages in current transaction
  • ora-01345 : must be a LogMiner coordinator process
  • 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.