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-09-2017
ORA-16816

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

  • ora-16178 : Cannot specify remote destinations in archivelog manual mode
  • ora-31205 : DBMS_LDAP: PL/SQL - Invalid LDAP Auth method.
  • ora-19754 : error reading from change tracking file
  • ora-14151 : invalid table partitioning method
  • ora-27513 : parameter string contains invalid value string
  • ora-12607 : TNS: Connect timeout occurred
  • ora-29836 : failed to validate referenced operators
  • ora-38709 : Recovery Area is not enabled.
  • ora-12728 : invalid range in regular expression
  • ora-13153 : invalid high water mark specified
  • ora-38740 : Usable blocks value string is not valid.
  • ora-31506 : duplicate subscription name string
  • ora-16166 : LGWR network server failed to send remote message
  • ora-13260 : layer table string does not exist
  • ora-16640 : CRS warns that multiple instances may still be running
  • ora-24236 : source text is empty
  • ora-25315 : unsupported configuration for propagation of buffered messages
  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-06959 : Buffer I/O quota is too small
  • ora-25473 : cannot store string in rule action context
  • ora-12329 : database string is closed; no operations are permitted
  • ora-13042 : invalid SDO_LEVEL and SDO_NUMTILES combination
  • ora-16735 : error executing dbms_logstdby.unskip_error procedure
  • ora-01952 : system privileges not granted to 'string'
  • ora-15047 : ASM file name 'string' is not in multiple-file creation form
  • ora-13918 : Updating system alert with reason_id string failed; previous alert not found
  • ora-29384 : number of children for plan string exceeds string
  • ora-08230 : smscre: failed to allocate SGA
  • 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.