ORA-28501: communication error on heterogeneous database link

Cause : nAu enpxceet docmmnucitaoi nafliru ecoucrrdeo n aehetoregenuo sadatabesl ni kota n noO-arlc eystsme .hT eemssga ebavo eiwllb eofllwodeb y aesocdnm seasegg neretadeb yht eocnnceet don-nrOcaels syet.m

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

eS eht eoducemtntaoi nof rht eon-nrOcaels syet mof rnae pxalanitnoo fht eesocdne rrrom seaseg.

update : 23-07-2017
ORA-28501

ORA-28501 - communication error on heterogeneous database link
ORA-28501 - communication error on heterogeneous database link

  • ora-00091 : LARGE_POOL_SIZE must be at least string
  • ora-01176 : data dictionary has more than the string files allowed by the controlfie
  • ora-23354 : deferred RPC execution disabled for "string" with "string"
  • ora-12995 : no columns in partially dropped state
  • ora-19565 : BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
  • ora-16782 : instance not open for read and write access
  • ora-31493 : could not prepare session for LogMiner session
  • ora-16043 : managed recovery session canceled
  • ora-27303 : additional information: string
  • ora-23404 : refresh group "string"."string" does not exist
  • ora-31095 : cannot generate string : "string.string" already exists
  • ora-16707 : the value of the property string is invalid, valid values are string
  • ora-29265 : HTTP header not found
  • ora-36999 : (XSRELGID16) OBJECT workspace object is not a surrogate dimension, a source relation must be specified when creating any non-surrogate grouping id.
  • ora-19654 : must use backup control file to switch file incarnations
  • ora-09773 : osnmgetdatmsg: message from host had incorrect message type
  • ora-00290 : operating system archival error occurred. See error below
  • ora-12665 : NLS string open failed
  • ora-01224 : group number in header string does not match GROUP string
  • ora-23430 : argument "string" cannot be NULL or empty string
  • ora-36342 : (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • ora-23434 : master site string not known for object group
  • ora-12345 : user string lacks CREATE SESSION privilege in database link (linkname string)
  • ora-13221 : unknown geometry type in the geometry object
  • ora-02060 : select for update specified a join of distributed tables
  • ora-25217 : enqueue failed, visibility must be IMMEDIATE for queue string.string
  • ora-12436 : no policy options specified
  • ora-01352 : tablespace given for Logminer spill does not exist
  • ora-16213 : ddl encountered, stopping apply engine
  • 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.