ORA-16617: unknown object identifier specified in request

Cause : The Data Guard broker returned this error because the object identifier specified in the request was invalid or unknown. For example, this error is returned if an invalid or unknown database object identifier is specified in a request that requires a database object identifier.

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

Verify that a valid object identifier was specified in the request and then reissue the request.

update : 27-06-2017

ORA-16617 - unknown object identifier specified in request
ORA-16617 - unknown object identifier specified in request

  • ora-01536 : space quota exceeded for tablespace 'string'
  • ora-08195 : Flashback Table operation is not supported on partitions
  • ora-01672 : control file may be missing files or have extra ones
  • ora-32625 : illegal dimension in cell reference predicate
  • ora-39217 : object type "string"."string" typeid mismatch
  • ora-13344 : an arcpolygon geometry has fewer than five coordinates
  • ora-01517 : log member: 'string'
  • ora-12664 : Services required by server not available on the client
  • ora-12716 : Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
  • ora-13386 : commit/rollback operation error: [string]
  • ora-36269 : (XSCGMDLAGG10) 'workspace object' does not exist or is not a dimension.
  • ora-30067 : Internal Event to turn on nested debugging info
  • ora-28031 : maximum of string enabled roles exceeded
  • ora-14160 : this physical attribute may not be specified for a table subpartition
  • ora-30118 : syntax error at 'string' at the end of input
  • ora-16120 : dependencies being computed for transaction at SCN string
  • ora-14501 : object is not partitioned
  • ora-00153 : internal error in XA library
  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-19232 : XQ0012 - imported schemas violate validity rules
  • ora-01019 : unable to allocate memory in the user side
  • ora-16080 : invalid LogMiner session string for APPLY
  • ora-00604 : error occurred at recursive SQL level string
  • ora-22897 : no scope clause specified for user-defined REF column "string"
  • ora-16095 : Dependent destination removal for inactivation
  • ora-01182 : cannot create database file string - file is in use or recovery
  • ora-13043 : failed to read metadata from the _SDOLAYER table
  • ora-26085 : direct path operation must start its own transaction
  • ora-25408 : can not safely replay call
  • ora-19682 : file string not in block media recovery context
  • 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.