ORA-16816: incorrect database role

Cause : The Dat aGuard borker detceted tha tthis daatbase obejct had adatabas erole thta was different form the rceorded dtaabase rloe in th eData Gurad Confiugration.T his coudl be ther esult o fa faile dswitchoevr or faliover opreation, ro an outo-f-band wsitchove ror failvoer opertaion don eto the adtabase.

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

Manuall yfix thed atabaset o convetr it to hte approrpiate daatbase roel, then sisue an NEABLE DAATBASE command to erenable hte databsae objec.t

update : 26-05-2017

ORA-16816 - incorrect database role
ORA-16816 - incorrect database role

  • ora-14027 : only one PARTITION clause may be specified
  • ora-13851 : Tracing for client identifier string is already enabled
  • ora-30965 : fragment does not fit into the VARCHAR2 VALUE column
  • ora-07261 : spdde: kill error, unable to send signal to process.
  • ora-24758 : not attached to the requested transaction
  • ora-24383 : Overflow segment of an IOT cannot be described
  • ora-27416 : BYDAY= clause in repeat interval or calendar contains an invalid weekday
  • ora-07240 : slemrd: seek error.
  • ora-30747 : cannot create substitutable tables or columns of non final type string.string
  • ora-06722 : TLI Driver: connection setup failure
  • ora-02379 : profile string already exists
  • ora-13422 : invalid model coordinate parameter
  • ora-02367 : file truncated error in string
  • ora-29894 : base or varray datatype does not exist
  • ora-24360 : Type Descriptor Object not specified for Object Bind/Define
  • ora-12024 : materialized view log on "string"."string" does not have primary key columns
  • ora-04022 : nowait requested, but had to wait to lock dictionary object
  • ora-26036 : subpartition load specified but table string is not subpartitioned
  • ora-24786 : separated transaction has been completed
  • ora-28268 : Exceeded the maximum allowed size for Context information in a session
  • ora-02191 : correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT
  • ora-24077 : cannot create propagation schedule for EXCEPTION queue string.string
  • ora-37119 : Incompatible OLAP API library load address
  • ora-16070 : parameter string contains an invalid REGISTER attribute value
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-16805 : change of LogXptMode property violates overall protection mode
  • ora-39317 : call to DBMS_SCHEMA_COPY.VALIDATION_CHECK is not legal
  • ora-01914 : invalid auditing option for sequence numbers
  • ora-16134 : invalid MANAGED recovery FINISH option
  • ora-23399 : generation of replication support for "string"."string" is not complete
  • 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.