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-04-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-10841 : Default un-inintialized charact set form to SQLCS_IMPLICIT
  • ora-34183 : (MXCHGDCL22) Partition number already exists.
  • ora-09361 : Windows 3.1 Two-Task driver unable to lock context area
  • ora-22163 : left hand and right hand side collections are not of same type
  • ora-28112 : failed to execute policy function
  • ora-16132 : An error occurred during activation of the standby.
  • ora-36678 : (XSDPART16) workspace object is missing from one or more partition dimension lists.
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • ora-13369 : invalid value for etype in the 4-digit format
  • ora-01581 : attempt to use rollback segment (string) new extent (string) which is being allocated
  • ora-19902 : incarnation key string not found
  • ora-37103 : (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
  • ora-12056 : invalid REFRESH method
  • ora-02215 : duplicate tablespace name clause
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-06306 : IPA: Message write length error
  • ora-16202 : Skip procedure requested to replace statement
  • ora-00482 : LMD* process terminated with error
  • ora-13840 : Concurrent DDL Error in create SQL profile operation.
  • ora-39030 : invalid file type string
  • ora-01425 : escape character must be character string of length 1
  • ora-16559 : out of memory at string
  • ora-24357 : internal error while converting from to OCIDate.
  • ora-30205 : invalid Character set
  • ora-13644 : The user "string" is invalid.
  • ora-25196 : keyword MOVE in ALTER TABLE MOVE must immediately follow
  • ora-29850 : invalid option for creation of domain indexes
  • ora-40222 : data mining model export failed, job name=string, error=string
  • ora-09974 : skxfidini: Error Initializing SDI Channel
  • ora-28157 : Proxy user 'string' forbidden to set role 'string' for client 'string'
  • 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.