ORA-12351: cannot create view using a remote object which has a remote object reference

Cause : Yo utreid ot cerat ea iveww hihc rfeernece sa ermoet ojbec twhcih,i n utrn ,reefrecnesa n bojetc o nantohe rdaatbaes. iSnc eth eviwe taht oyu rtie dtoc retae erfeerncse ar emtoe bojetc, htato bjcet acnnto rfeernecea n bojetc o nantohe rdaatbaes.

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

Choosea dfifeernto bjcet ot rfeernecei n oyurv ie worc hagne hte ermoet ojbec tsot ha titd oe sno treefrecne naotehr adtaabse.

update : 24-09-2017

ORA-12351 - cannot create view using a remote object which has a remote object reference
ORA-12351 - cannot create view using a remote object which has a remote object reference

  • ora-24064 : propagation for QUEUE string and DESTINATION string already enabled
  • ora-15005 : name "string" is already used by an existing alias
  • ora-01235 : END BACKUP failed for string file(s) and succeeded for string
  • ora-29959 : error in the execution of the string routine for one or more of the index partitions
  • ora-26091 : requested direct path operation not supported
  • ora-01239 : database must be in ARCHIVELOG mode to use external cache
  • ora-00271 : there are no logs that need archiving
  • ora-29863 : warning in the execution of ODCIINDEXCREATE routine
  • ora-13217 : invalid parameters supplied in ALTER INDEX statement
  • ora-36800 : (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP
  • ora-30186 : '' must be followed by four hexdecimal characters or another ''
  • ora-19101 : CONTENT keyword expected
  • ora-33308 : (DBVALID04) SEVERE ERROR: Record number used but not allocated
  • ora-26522 : rpc execution error
  • ora-39780 : Direct path context operations are not allowed after the context is aborted or finished
  • ora-03252 : initial extent size not enough for LOB segment
  • ora-00041 : active time limit exceeded - session terminated
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-01463 : cannot modify column datatype with current constraint(s)
  • ora-00302 : limit of string logs exceeded
  • ora-32132 : maximum iterations cannot be changed
  • ora-34361 : (MXDSS12) number other user reading
  • ora-34358 : (MXDSS14) number other users reading
  • ora-10690 : Set shadow process core file dump type (Unix only)
  • ora-39062 : error creating master process string
  • ora-12476 : least upper bound resulted in an invalid OS label
  • ora-24093 : AQ agent string not granted privileges of database user string
  • ora-02831 : Segment deallocation failed - empty segment list
  • ora-37143 : (XSSQLMDQ03) string is not a valid analytic workspace name.
  • ora-24388 : Unsupported functionality in fast path mode
  • 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.