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 : 22-08-2017
ORA-16802

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

  • ora-22855 : optional name for LOB storage segment incorrectly specified
  • ora-32626 : illegal bounds or increment in MODEL FOR loop
  • ora-27434 : cannot alter chain step job string.string.string
  • ora-14309 : Total count of list values exceeds maximum allowed
  • ora-38480 : creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed.
  • ora-29818 : column name not properly specified
  • ora-27474 : cannot give both an argument name and an argument position
  • ora-27546 : Oracle compiled against IPC interface version string.string found version string.string
  • ora-16582 : could not edit instance specific property
  • ora-39127 : unexpected error from call to string string
  • ora-14008 : missing THAN keyword
  • ora-01202 : wrong incarnation of this file - wrong creation time
  • ora-26034 : Column string does not exist in stream
  • ora-38798 : Cannot perform partial database recovery
  • ora-23367 : table string is missing the primary key
  • ora-21700 : object does not exist or is marked for delete
  • ora-16724 : the intended state for the database has been set to OFFLINE
  • ora-22290 : operation would exceed the maximum number of opened files or LOBs
  • ora-03250 : Cannot mark this segment corrupt
  • ora-19242 : XQ0022 - namespace declaration attribute must be a literal
  • ora-36950 : (XSFCAST22) The list of string values cannot have more than number members. You supplied number.
  • ora-23601 : PROPAGATION_NAME string does not exist
  • ora-09811 : Unable to initialize package.
  • ora-06142 : NETTCP: error getting user information
  • ora-29256 : Cursor contains both regular and array defines which is illegal
  • ora-19908 : datafile string has invalid checkpoint
  • ora-02306 : cannot create a type that already has valid dependent(s)
  • ora-32774 : more than one file was specified for bigfile tablespace string
  • ora-09957 : Unable to send termination request to IMON
  • ora-24344 : success with compilation error
  • 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.