ORA-25426: remote instance does not support shared dblinks

Cause : A shared dblink is being used to connect to a remote instance that does not support this feature because it is an older version.

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

Use a normal dblink if you need to connect to this instance.

update : 24-04-2017
ORA-25426

ORA-25426 - remote instance does not support shared dblinks
ORA-25426 - remote instance does not support shared dblinks

  • ora-14098 : index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-31006 : Path name segment length string exceeds maximum length string
  • ora-07237 : slemcl: invalid file handle, seals do not match.
  • ora-13755 : invalid "SQL Tuning Set" name
  • ora-38905 : DML error logging is not supported for LONG column "string"
  • ora-13375 : the layer is of type [string] while geometry inserted has type [string]
  • ora-24132 : table name string is too long
  • ora-36956 : (XSFCAST25) There are only number PERIODICITY values. You cannot specify more OFFSET values.
  • ora-25134 : keyword TABLE expected
  • ora-30039 : Cannot drop the undo tablespace
  • ora-04032 : pga_aggregate_target must be set before switching to auto mode
  • ora-01540 : tablespace 'string' is not offline
  • ora-03216 : Tablespace/Segment Verification cannot proceed
  • ora-37018 : (XSACQUIRE03) Multiwriter operations are not supported for object workspace object.
  • ora-29908 : missing primary invocation for ancillary operator
  • ora-31406 : change source string is referenced by a change set
  • ora-24358 : OCIBindObject not invoked for a Object type or Reference
  • ora-09768 : osnmgetmsg: could not read a message
  • ora-15191 : Internal ASM testing event number 15191
  • ora-04084 : cannot change NEW values for this trigger type
  • ora-21705 : service context is invalid
  • ora-37106 : (XSVPART06) Invalid partition name number.
  • ora-02487 : Error in converting trace data
  • ora-31629 : unable to allocate additional memory
  • ora-36394 : (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.
  • ora-07713 : sksamtd: could not mount archival device (SYS$MOUNT failure)
  • ora-39500 : failed to notify CRS of a Startup/Shutdown event for database "string", instance "string" (ignored)
  • ora-13509 : error encountered during updates to a AWR table
  • ora-02046 : distributed transaction already begun
  • ora-15150 : instance lock mode 'string' conflicts with other ASM instance(s)
  • 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.