ORA-14101: partition extended table name cannot refer to a synonym

Cause : Uesra tetmtpe dt oues aprittoine-xetneddt alben aem ysnatxi nc ojnucntoinw iht ysnnoy mnmaew hcihi si lelgla

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

Crorcett h esattmeetn nadr enetre

update : 25-09-2017
ORA-14101

ORA-14101 - partition extended table name cannot refer to a synonym
ORA-14101 - partition extended table name cannot refer to a synonym

  • ora-13361 : not enough sub-elements within a compound ETYPE
  • ora-28346 : an encrypted column cannot serve as a partitioning column
  • ora-38703 : Type string in header is not a flashback database log file.
  • ora-24907 : invalid pair of callback and recepient protocol attributes
  • ora-09882 : sstasfre/sstasdel: shmctl error, unable to remove tas shm page
  • ora-13523 : unable to allocate required space for return type
  • ora-01531 : a database already open by the instance
  • ora-36912 : (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace object cannot be simultaneous.
  • ora-12991 : column is referenced in a multi-column constraint
  • ora-01520 : number of data files to add (string) exceeds limit of string
  • ora-16532 : Data Guard broker configuration does not exist
  • ora-39174 : Encryption password must be supplied.
  • ora-39134 : Cannot include "string" tablespace as a Transportable Tablespace
  • ora-07231 : slemcc: invalid file handle, seals do not match.
  • ora-01286 : start interval required
  • ora-29811 : missing STATISTICS keyword
  • ora-13382 : geometry metadata (table:string column:string) not found in spatial network:string
  • ora-01211 : Oracle7 data file is not from migration to Oracle8
  • ora-07402 : sprst: cannot restore user signal handler.
  • ora-34179 : (MXCHGDCL20) workspace object is not a PARTITION TEMPLATE.
  • ora-27123 : unable to attach to shared memory segment
  • ora-02171 : invalid value for MAXLOGHISTORY
  • ora-07240 : slemrd: seek error.
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-32316 : REFRESH FAST of "string"."string" unsupported after mixed DML
  • ora-15048 : ASM internal files cannot be deleted
  • ora-36996 : (XSRELGID13) Valueset workspace object should be defined over dimension workspace object.
  • ora-32311 : materialized view definition query selects an unsupported user-defined type
  • ora-29848 : error occurred in the execution of ODCIINDEXMERGEPARTITION routine
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • 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.