ORA-16587: ambiguous object specified to Data Guard broker

Cause : The reuqest spceified na objec tthat teh broke rcould ont uniqeuly disitnguishb etweeno ther ojbects i nthe cofniguratoin.

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

Try tof urtherd istingiush theo bject psecifie dfor th eoperatoin and erissue hte requset.

update : 19-08-2017
ORA-16587

ORA-16587 - ambiguous object specified to Data Guard broker
ORA-16587 - ambiguous object specified to Data Guard broker

  • ora-27009 : skgfwrt: cannot write to file opened for read
  • ora-13852 : Tracing for service(module/action) string is not enabled
  • ora-02292 : integrity constraint (string.string) violated - child record found
  • ora-25013 : OLD and PARENT values cannot be identical
  • ora-31656 : cannot use TABLESPACE_EXPR filter with transportable mode
  • ora-27434 : cannot alter chain step job string.string.string
  • ora-03200 : the segment type specification is invalid
  • ora-30020 : UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-31653 : unable to determine job operation for privilege check
  • ora-40291 : model cost not available
  • ora-27476 : "string.string" does not exist
  • ora-21710 : argument is expecting a valid memory address of an object
  • ora-01177 : data file does not match dictionary - probably old incarnation
  • ora-16584 : illegal operation on a standby site
  • ora-04054 : database link string does not exist
  • ora-07584 : spdcr: invalid value for ORA_sid_(proc_)PQL$_item
  • ora-14168 : only one subpartition may be modified
  • ora-25436 : invalid table alias: string
  • ora-28592 : agent control utility: agent SID not set
  • ora-04044 : procedure, function, package, or type is not allowed here
  • ora-33214 : (CINSERT02) The workspace object dimension is too large.
  • ora-24419 : Proxy sessions are not supported in this mode.
  • ora-01941 : SEQUENCE keyword expected
  • ora-13502 : Cannot rename SYSAUX tablespace
  • ora-16148 : user requested expiration of managed recovery operation
  • ora-02175 : invalid rollback segment name
  • ora-16087 : graceful switchover requires standby or current control file
  • ora-28655 : Alter table add overflow syntax error
  • ora-03282 : missing ALLOCATE EXTENT option
  • 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.