ORA-16575: request terminated at broker discretion

Cause : This status is returned when the broker terminates a user- initiated request. The broker will terminate all other current and pending requests when it begins processing a failover request. These other requests are terminated with this status.

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

There is no action to be taken.

update : 18-08-2017

ORA-16575 - request terminated at broker discretion
ORA-16575 - request terminated at broker discretion

  • ora-24903 : invalid namespace attribute passed into OCI call
  • ora-12919 : Can not drop the default permanent tablespace
  • ora-15193 : Internal ASM tracing event number 15193
  • ora-01533 : cannot rename file 'string'; file does not belong to tablespace
  • ora-23621 : Operation corresponding to script string is in progress.
  • ora-02899 : smscre: Cannot create SGA with Extended Shared Memory feature
  • ora-36223 : (XSLPDSC04) object workspace object in IGNORE or DENSE list has illegal type
  • ora-19587 : error occurred reading string bytes at block number string
  • ora-16543 : invalid request made to broker
  • ora-24127 : TABLESPACE parameter specified with an ACTION other than CREATE_ACTION
  • ora-29326 : SET COMPATIBILITY release number higher than string
  • ora-24316 : illegal handle type
  • ora-40286 : remote operations not permitted on mining models
  • ora-31616 : unable to write to dump file "string"
  • ora-00317 : file type string in header is not log file
  • ora-16015 : log string sequence# string not archived, media recovery disabled
  • ora-03200 : the segment type specification is invalid
  • ora-13029 : Invalid SRID in the SDO_GEOMETRY object
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-19657 : cannot inspect current datafile string
  • ora-31046 : Incorrect argument(s) specified in the operator
  • ora-13438 : GeoRaster metadata pyramid type error
  • ora-00153 : internal error in XA library
  • ora-19757 : could not resize change tracking file to string blocks
  • ora-09914 : Unable to open the ORACLE password file.
  • ora-09292 : sksabln: unable to build archive file name
  • ora-19211 : column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
  • ora-28120 : driving context already exists
  • ora-27461 : The value for attribute string is too large.
  • ora-01315 : Log file has been added or removed during select
  • 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.