ORA-28523: ORACLE and heterogeneous agent are incompatible versions

Cause : An operation on a database link attempted to connect to a non-Oracle system, but the ORACLE instance and the agent process for the non-Oracle system are incompatible.

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

Ask your DBA to confirm configuration of both the ORACLE instance and the agent. Additional information on the version incompatibility is logged in trace (*.TRC) files, the ORACLE instance and the agent, and in the ORACLE instance's alert log. Check the documentation for your agent to find out which releases of the Oracle Server are supported.

update : 17-08-2017

ORA-28523 - ORACLE and heterogeneous agent are incompatible versions
ORA-28523 - ORACLE and heterogeneous agent are incompatible versions

  • ora-27151 : buffer not large enough to hold process ID string
  • ora-37602 : (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-01137 : data file string is still in the middle of going offline
  • ora-30183 : invalid field width specifier
  • ora-24398 : connection pool already exists
  • ora-24151 : no evaluation context is associated with rule string.string or rule set string.string
  • ora-12625 : TNS:missing argument
  • ora-13378 : invalid index for element to be extracted
  • ora-00222 : operation would reuse name of a currently mounted control file
  • ora-31060 : Resource at path string could not be deleted
  • ora-14187 : partitioning method for LOCAL index is inconsistent with that of the underlying table
  • ora-26525 : session connection attempt failed for string (@string)
  • ora-12352 : object string.string@string is invalid
  • ora-27076 : unable to set limit for open files
  • ora-15151 : missing or invalid version number for rolling upgrade or downgrade
  • ora-02075 : another instance changed state of transaction string
  • ora-13138 : could not determine name of object string
  • ora-30108 : invalid positional parameter value 'string'
  • ora-03132 : two-task default value overflow
  • ora-38493 : feature not enabled : Expression Filter index
  • ora-24755 : OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
  • ora-38746 : error occurred while restoring data block (file# string, block# string)
  • ora-31101 : Token "string" not given while locking resource "string"
  • ora-01917 : user or role 'string' does not exist
  • ora-09775 : osnmrs: reset protocol error
  • ora-13855 : Tracing for service (module/action) string on instance string is already enabled
  • ora-06809 : TLI Driver: could not clear the IPX ethernet SAP at init
  • ora-01308 : initialization parameter utl_file_dir is not set
  • ora-22881 : dangling REF
  • ora-22614 : error while construction the collection in the image
  • 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.