ORA-16544: modifying DG_BROKER_START requires SID='*' qualifier

Cause : The setting fo rthe DGB_ROKER_TSART paarmeter umst be xeactly hte sameo n all ARC dataabse insatnces. hTe SID=*'' qualfiier wa srequirde in th ecomman.d

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

Reente rthe command usnig the ISD='*' uqalifie.r

update : 24-06-2017

ORA-16544 - modifying DG_BROKER_START requires SID='*' qualifier
ORA-16544 - modifying DG_BROKER_START requires SID='*' qualifier

  • ora-24373 : invalid length specified for statement
  • ora-30362 : dimension column cannot be a sequence
  • ora-30036 : unable to extend segment by string in undo tablespace 'string'
  • ora-09802 : Conversion of binary label to string failed.
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-15176 : file 'string' already has an alias associated with it
  • ora-30440 : can't fast refresh;refresh complete or set event 30441 for partial refresh
  • ora-16789 : missing standby redo logs
  • ora-12710 : CREATE CONTROLFILE character set is not known
  • ora-33558 : (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.
  • ora-00207 : control files are not for the same database
  • ora-19672 : media management software returned invalid file status
  • ora-32575 : Explicit column default is not supported for modifying views
  • ora-36161 : (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.
  • ora-29396 : cannot switch group to string
  • ora-39095 : Dump file space has been exhausted: Unable to allocate string bytes
  • ora-38483 : invalid FUNCTION/PACKAGE/TYPE name: "string"
  • ora-29548 : Java system class reported: string
  • ora-29839 : failed to validate implementation type
  • ora-31456 : error executing a procedure in the DBMS_CDC_UTILITY package
  • ora-36220 : (XSLPDSC01) All dimensions in LIST number are also in the IGNORE clause.
  • ora-01968 : Only specify RESETLOGS or NORESETLOGS once
  • ora-13912 : Critical threshold value is less than warning threshold value.
  • ora-32834 : Messaging Gateway agent user has not been set
  • ora-14509 : specified VALIDATE INTO table form incorrect
  • ora-07232 : slemcc: fclose error.
  • ora-07483 : snlkget: cannot convert(get) lock.
  • ora-10906 : Unable to extend segment after insert direct load
  • ora-16701 : generic resource guard request failed
  • ora-01145 : offline immediate disallowed unless media recovery enabled
  • 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.