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 : 30-04-2017
ORA-16575

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

  • ora-25467 : table alias not specified
  • ora-31601 : Function string cannot be called now that fetch has begun.
  • ora-30383 : specified dimension level does not exist in the attribute
  • ora-32024 : invalid directory specified for audit_file_dest parameter
  • ora-22289 : cannot perform string operation on an unopened file or LOB
  • ora-14108 : illegal partition-extended table name syntax
  • ora-13517 : Baseline (id = string) does not exist
  • ora-23399 : generation of replication support for "string"."string" is not complete
  • ora-31630 : a job name is required to attach a job for user string
  • ora-15041 : diskgroup space exhausted
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-02070 : database stringstring does not support string in this context
  • ora-13203 : failed to read USER_SDO_GEOM_METADATA view
  • ora-00127 : dispatcher string does not exist
  • ora-09927 : Unable to set label of server
  • ora-31027 : Path name or handle string does not point to a resource
  • ora-16637 : an instance failed to access the Data Guard broker configuration
  • ora-24151 : no evaluation context is associated with rule string.string or rule set string.string
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • ora-15053 : diskgroup "string" contains existing files
  • ora-06755 : TLI Driver: cannot close transport endpoint
  • ora-36882 : (XSSRF01) The second parameter of an AW single row function cannot be NULL.
  • ora-33332 : (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.
  • ora-15003 : diskgroup "string" already mounted in another lock name space
  • ora-19663 : cannot apply current offline range to datafile string
  • ora-22345 : recompile type string.string before attempting this operation
  • ora-14159 : duplicate subpartition name
  • ora-14113 : partitioned table cannot have column with LOB datatype
  • ora-16574 : switchover disallowed when required databases are offline
  • ora-02719 : osnfop: fork failed
  • 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.