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 : 16-08-2017

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

  • ora-09847 : soacon: ARCH unable to open named pipe.
  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-14279 : index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-19639 : file string is more current than this incremental backup
  • ora-19726 : cannot plug data [string] at level string into database running at compatibility level string
  • ora-31226 : DBMS_LDAP: MOD_ARRAY size limit exceeded
  • ora-30438 : unable to access named pipe 'string'
  • ora-29908 : missing primary invocation for ancillary operator
  • ora-07222 : slspool: line printer spooler command exited with an error.
  • ora-07451 : slskstat: unable to obtain load information.
  • ora-25463 : table alias not specified
  • ora-40261 : input data for model build contains negative values
  • ora-19870 : error reading backup piece string
  • ora-02816 : Unable to kill a process
  • ora-19163 : XP0004 - XQuery type mismatch: argument type mismatch: expected - 'string' got - 'string' for function 'string'
  • ora-02783 : Both post and wait functions were not specified
  • ora-16532 : Data Guard broker configuration does not exist
  • ora-22812 : cannot reference nested table column's storage table
  • ora-09796 : szrbuild: malloc of role name failed.
  • ora-16214 : apply stalled for apply delay
  • ora-12667 : Shared server: outbound transport protocol different from inbound
  • ora-01935 : missing user or role name
  • ora-27071 : unable to seek to desired position in file
  • ora-07586 : spdcr: $SEARCH failure
  • ora-12500 : TNS:listener failed to start a dedicated server process
  • ora-26681 : command type not supported
  • ora-36341 : (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
  • ora-25335 : AQ array operations not allowed for buffered messages
  • ora-00220 : control file not mounted by first instance, check alert log for more info
  • ora-32830 : result code string returned by Messaging Gateway agent
  • 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.