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 : 23-04-2017
ORA-16587

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

  • ora-19510 : failed to set size of string blocks for file "string" (blocksize=string)
  • ora-04046 : results of compilation are too large to support
  • ora-39777 : data saves are not allowed when loading lob columns
  • ora-00337 : log file 'string' does not exist and no size specified
  • ora-02820 : Unable to write the requested number of blocks
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-22870 : ALTER TYPE with REPLACE option a non-object type
  • ora-00275 : media recovery has already been started
  • ora-02377 : invalid resource limit
  • ora-33332 : (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.
  • ora-01088 : cannot shut down ORACLE while active processes exist
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-24234 : unable to get source of string "string"."string", insufficient privileges or does not exist
  • ora-06518 : PL/SQL: Probe version string incompatible with version string
  • ora-39109 : Unprivileged users may not operate upon other users' schemas
  • ora-01626 : rollback segment number 'string' cannot handle more transactions
  • ora-31605 : the following was returned from string in routine string: LPX-number: string
  • ora-26097 : unsupported conversion for column string (from type number to type number)
  • ora-33334 : (DSSEXIST04) Analytic workspace string is not attached.
  • ora-27122 : unable to protect memory
  • ora-16554 : translation not valid
  • ora-36763 : (XSAGGCNTMOVE01) Aggregation variable workspace object cannot have itself as an AGGCOUNT.
  • ora-25957 : join index where clause cannot contain cycles
  • ora-02200 : WITH GRANT OPTION not allowed for PUBLIC
  • ora-06528 : Error executing PL/SQL profiler
  • ora-19561 : %s requires a DISK channel
  • ora-12842 : Cursor invalidated during parallel execution
  • ora-02766 : Invalid maximum of request descriptors
  • ora-02201 : sequence not allowed here
  • ora-31042 : Too many properties in type 'string'
  • 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.