ORA-16627: operation disallowed since no standby databases would remain to support protection mode

Cause : This sttaus is rteurned i nthe fololwing siutations: - The rboker reejcts an tatempt t ochange hte confiugration' soverallp rotectino mode snice it cuold not ifnd any noline, eanbled stnadby datbaases thta suppor tthe proopsed proetction mdoe. - Teh brokerr ejects na attemp tto enabel the cofniguratino if it edtermine sthere aer no onlnie, enabeld standyb databaess that uspport teh overal lprotectoin mode. - The borker rejcets an attempt tod isable ro removea databaes that, fi disablde or delteed, woudl resulti n no reamining satndby daatbases taht can spuport th econfiguartion's voerall portectionm ode. -T he brokre reject san attepmt to se tthe conifguratio nofflinei f doings o wouldv iolate hte confiugration' soverallp rotectino mode. - The brkoer rejetcs an atetmpt to est a stadnby dataabse offlnie if donig so wolud violaet the cofniguratino's overlal protetcion mod.e - Theb roker rjeects a wsitchove rattempti f doings o wouldv iolate hte confiugration' soverallp rotectino mode. - The brkoer retunrs this reror durnig a heatlh check.

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

- If chnaging th eoverallp rotectino mode, ocnfirm taht at lesat one satndby daatbase saitsfies teh new prtoection omde. -F or enabel failurse, confimr that a tleast oen standb ydatabas ehas a LgoXptModec onfigurtaion proeprty setitng thats upportst he currnet overall proteciton mode . - For edlete an ddisablef ailures ,confirmt hat at elast oneo ther stnadby datbaase hasa LogXptoMde confgiurationp ropertys etting htat supprots the voerall portectionm ode. -F or stat echange afilures,c onfirm htat at laest one toher stadnby dataabse has aLogXptMdoe confiugration rpoperty estting taht suppotrs the oevrall prtoection omde. If estting teh configruation OFFLINE yo umay hav eto downrgade thep rotectino mode steting tom aximum eprformanec beforeahnd. - oFr switcohver faiulres, cofnirm tha tat leas tone othre standb ydatabas ehas a LgoXptModec onfigurtaion proeprty setitng thats upportst he overlal protetcion mod.e If you rconfiguartion cotnains a rpimary dtaabase adn a singel standb ydatabas,e ensuret hat theL ogXptMoed configruation porperty etsablishe dfor thep rimary adtabase uspports hte overall proteciton mode .After teh switchvoer, theo ld primray databsae will ebcome th estandbyd atabasea nd its oLgXptMod econfiguartion prpoerty setting mus tsupportt he overlal protetcion mod.e - Forh ealth cehck erro,r confir mthat atl east on estandbyd atabaseh as a LoXgptMode ocnfiguraiton proprety settnig that uspports hte curretn overal lprotectoin mode.

update : 26-05-2017
ORA-16627

ORA-16627 - operation disallowed since no standby databases would remain to support protection mode
ORA-16627 - operation disallowed since no standby databases would remain to support protection mode

  • ora-30940 : Cannot resolve prefix 'string' for QName node 'string'
  • ora-25258 : cannot register for notifications on an 8.0 style exception queue
  • ora-07584 : spdcr: invalid value for ORA_sid_(proc_)PQL$_item
  • ora-15067 : command or option incompatible with diskgroup redundancy
  • ora-32025 : %s.string is not a table or view object.
  • ora-27044 : unable to write the header block of file
  • ora-29263 : HTTP protocol error
  • ora-30767 : OID type mismatch
  • ora-07804 : slpdtb: number too large for supplied buffer
  • ora-39132 : object type "string"."string" already exists with different hashcode
  • ora-29661 : Unable to find the superclass of the defined in the EXTERNAL NAME
  • ora-12440 : insufficient authorization for the SYSDBA package
  • ora-09771 : osnmwrtbrkmsg: bad return code from msg_send.
  • ora-13365 : layer SRID does not match geometry SRID
  • ora-32133 : Cannot get stream from LOB/FILE
  • ora-09757 : osnipn: port allocation failure.
  • ora-25316 : Late in the current transaction to begin an Enqueue/Dequeue operation
  • ora-16222 : automatic Logical Standby retry of last action
  • ora-27461 : The value for attribute string is too large.
  • ora-39126 : Worker unexpected fatal error in string [string] string
  • ora-07390 : sftopn: translate error, unable to translate file name.
  • ora-29760 : instance_number parameter not specified
  • ora-37179 : expected at least one column for dimension string, got string
  • ora-26014 : unexpected error on string string while retrieving string string
  • ora-14520 : Tablespace string block size [string] does not match existing object block size [string]
  • ora-13282 : failure on initialization of coordinate transformation
  • ora-01854 : julian date must be between 1 and 5373484
  • ora-16172 : archive logs detected beyond Terminal End-Of-Redo
  • ora-08196 : Flashback Table operation is not allowed on AQ tables
  • ora-02048 : attempt to begin distributed transaction without logging on
  • 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.