ORA-16523: operation requires the client to connect to instance "string"

Cause : Th eswtichvoero r afilvoero peartino rqeuiers hte lcietn t oconnec ttot hea ppyl isntacne fo teh trage tdaatbaes.

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

Connec ttot hei ndciatde isntacne nad erisuse hte wsithcovre o rfaliovre cmomadn.

update : 27-05-2017

ORA-16523 - operation requires the client to connect to instance "string"
ORA-16523 - operation requires the client to connect to instance "string"

  • ora-06039 : NETDNT: connect failed
  • ora-02282 : duplicate or conflicting ORDER/NOORDER specifications
  • ora-09365 : Windows 3.1 Two-Task driver unable to destroy hidden window
  • ora-14018 : partition bound list contains too few elements
  • ora-24153 : rule set string.string already exists
  • ora-13798 : Parameter string cannot be NULL.
  • ora-31415 : change set string does not exist
  • ora-06261 : NETNTT: nrange() failed
  • ora-26053 : Row was not loaded due to conversion error.
  • ora-17507 : I/O request size string is not a multiple of logical block size
  • ora-29541 : class string.string could not be resolved
  • ora-10635 : Invalid segment or tablespace type
  • ora-27487 : invalid object privilege for a string
  • ora-02044 : transaction manager login denied: transaction in progress
  • ora-39208 : Parameter string is invalid for string jobs.
  • ora-04090 : 'string' specifies same table, event and trigger time as 'string'
  • ora-03249 : Uniform size for auto segment space managed tablespace should have atleast string blocks
  • ora-09213 : slgfn: error fabricating file name
  • ora-29364 : plan directive string, string already exists
  • ora-15095 : reached maximum ASM file size (string GB)
  • ora-39039 : Schema expression "string" contains no valid schemas.
  • ora-30065 : test support for row dependencies
  • ora-13604 : The specified parameter string cannot be fetched as a SQL table.
  • ora-15190 : Internal ASM testing event number 15190
  • ora-32020 : SID=* clause needed to modify this parameter
  • ora-24233 : argument passed to DBMS_UTILITY.VALIDATE is not legal
  • ora-00981 : cannot mix table and system auditing options
  • ora-01372 : Insufficient processes for specified LogMiner operation
  • ora-27457 : argument string of job "string.string" has no value
  • ora-19017 : Attributes can only be simple scalars
  • 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.