ORA-24778: cannot open connections

Cause : The migratable transaction tried to access a remote database when the session itself had opened connections to remote database(s).

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

Close the connection(s) in the session and then try to access the remote database from the migratable transaction. If the error still occurs, contact Oracle customer support.

update : 24-05-2017
ORA-24778

ORA-24778 - cannot open connections
ORA-24778 - cannot open connections

  • ora-28504 : ROWID not found in ROWID cache for heterogeneous database link
  • ora-06403 : Unable to allocate memory.
  • ora-24785 : Cannot resume a non-migratable transaction
  • ora-14325 : only LOCAL indexes may be specified in this clause
  • ora-32636 : Too many rules in MODEL
  • ora-09927 : Unable to set label of server
  • ora-39082 : Object type string created with compilation warnings
  • ora-26011 : Cannot load type string into column string in table string
  • ora-01792 : maximum number of columns in a table or view is 1000
  • ora-29657 : class defined in EXTERNAL NAME clause is used in another subtype
  • ora-38418 : ADT associated with the attribute set string does not exist
  • ora-24814 : operation not allowed for temporary LOBs
  • ora-24371 : data would not fit in current prefetch buffer
  • ora-31439 : subscription is already active
  • ora-28291 : No Kerberos Principal Value found.
  • ora-12479 : file label string must equal DBHIGH string
  • ora-06011 : NETASY: dialogue too long
  • ora-24389 : Invalid scrollable fetch parameters
  • ora-02704 : osndopop: fork failed
  • ora-16595 : NetSlave process string failed to terminate
  • ora-25280 : complete sender information not provided to non-repudiate sender
  • ora-12423 : invalid position specified
  • ora-16649 : database will open after Data Guard broker has evaluated Fast-Start Failover status
  • ora-22292 : Cannot open a LOB in read-write mode without a transaction
  • ora-32500 : Dirname 'string' cannot exceed 'number' characters
  • ora-01270 : %s operation is not allowed if STANDBY_PRESERVES_NAMES is true
  • ora-00439 : feature not enabled: string
  • ora-38952 : Source database not 10.0.0.0 compatible
  • ora-04075 : invalid trigger action
  • ora-01325 : archive log mode must be enabled to build into the logstream
  • 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.