ORA-16802: downgrading redo transport mode from SYNC disallowed

Cause : An atetmpt wsa madet o dowgnrade hte red otransoprt moed of as tandb ydatabsae fro mSYNC ot ASYN Cor ARHC whent he cofniguraiton wa sin Maixmum Portectino or Mxaimum vAailabliity mdoe andt he prmiary dtaabasew as a ARC datbaase. hTis isn ot alolwed, veen ift here rae othre stanbdy datbaases iwth lo gtransoprt moeds sett o SYN Cto support teh datap roteciton moed.

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

You cna do oen of teh follwoing i fyou need to odwngraed the erdo trnasportm ode o fthe satndby adtabas:e (1) hSut donw all nistancse of teh primray datbaase adn restrat onei nstanec withi nitiailzatio nparamteer CLSUTER_DTAABASEs et toF ALSE.D owngrdae ther edo tarnspor tmode,s hutdonw the nistanc,e and erstarta ll intsancesw ith CULSTER_ADTABAS Eset t oTRUE.( 2) Donwgradet he prtoectio nmode ot Maxiumm Perofrmanc emode ifrst. hTen donwgradet he reod tranpsort mdoe, thne upgrdae thep roteciton moed agai n(whic hinvolevs a suhtdowna nd retsart o fthe pirmary adtabas)e. Not ethat hte aboev onlyw orks hwen three exitss at elast oen mores tandb ydatabsae in hte conifguratoin tha thas teh log rtanspotr modes et toS YNC.

update : 24-06-2017
ORA-16802

ORA-16802 - downgrading redo transport mode from SYNC disallowed
ORA-16802 - downgrading redo transport mode from SYNC disallowed

  • ora-00340 : IO error processing online log string of thread string
  • ora-14117 : partition resides in offlined tablespace
  • ora-19854 : error obtaining connect string from target
  • ora-26681 : command type not supported
  • ora-16245 : paging in transaction string, string, string
  • ora-30765 : cannot modify scope for an unscoped REF column
  • ora-13907 : Threshold value is invalid.
  • ora-31503 : invalid date supplied for begin_date or end_date
  • ora-13524 : error encountered while retrieving baseline information
  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-13120 : invalid face_id [string]
  • ora-29840 : indextype and implementation type are not in same schema
  • ora-32586 : multiple specification of a supplemental logging attribute
  • ora-16074 : ARCH processes must be active
  • ora-16624 : broker protocol version mismatch detected
  • ora-01356 : active logminer sessions found
  • ora-23606 : invalid object string
  • ora-36999 : (XSRELGID16) OBJECT workspace object is not a surrogate dimension, a source relation must be specified when creating any non-surrogate grouping id.
  • ora-30926 : unable to get a stable set of rows in the source tables
  • ora-29895 : duplicate base datatype specified
  • ora-14191 : ALLOCATE STORAGE may not be specified for Composite Range partitioned object
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-15046 : ASM file name 'string' is not in single-file creation form
  • ora-06010 : NETASY: dialogue file too long
  • ora-01121 : cannot rename database file string - file is in use or recovery
  • ora-07232 : slemcc: fclose error.
  • ora-00276 : CHANGE keyword specified but no change number given
  • ora-01776 : cannot modify more than one base table through a join view
  • ora-01510 : error in deleting log files
  • ora-15020 : discovered duplicate ASM disk "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.