ORA-16507: unrecognized request identifier

Cause : The specified request identifier was not recognized by the Data Guard broker.

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

Reissue the request using a valid request identifier.

update : 27-04-2017

ORA-16507 - unrecognized request identifier
ORA-16507 - unrecognized request identifier

  • ora-00087 : command cannot be executed on remote instance
  • ora-31609 : error loading file "string" from file system directory "string"
  • ora-00106 : cannot startup/shutdown database when connected to a dispatcher
  • ora-28029 : could not authorize remote server for user string
  • ora-01662 : tablespace 'string' is non-empty and cannot be made temporary
  • ora-16815 : incorrect redo transport setting for AlternateLocation for standby database "string"
  • ora-02703 : osnpopipe: pipe creation failed
  • ora-32330 : invalid operation on online redefinition interim table "string"."string"
  • ora-12436 : no policy options specified
  • ora-19271 : XP0051 - invalid atomic type definition
  • ora-25184 : column name expected
  • ora-31687 : error creating worker process string with worker id string
  • ora-14605 : Name missing for subpartition / lob segment in template
  • ora-16624 : broker protocol version mismatch detected
  • ora-02287 : sequence number not allowed here
  • ora-10941 : trace name context forever
  • ora-30087 : Adding two datetime values is not allowed
  • ora-37138 : (XSCCOMP13) You cannot delete values from workspace object because it is an aggregated COMPRESSED COMPOSITE.
  • ora-26094 : stream format error: input column overflow
  • ora-32510 : cannot create watchpoint on unreadable memory
  • ora-27103 : internal error
  • ora-26718 : transaction limit reached
  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • ora-28658 : This operation is supported only for Index-Organized tables
  • ora-31210 : DBMS_LDAP: PL/SQL - LDAP get_dn error.
  • ora-15162 : cluster in rolling downgrade
  • ora-19573 : cannot obtain string enqueue for datafile string
  • ora-26013 : List allocated may not be big enough
  • ora-01082 : 'row_locking = always' requires the transaction processing option
  • ora-29837 : insufficient privileges to execute implementation type
  • 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.