ORA-16801: redo transport-related property is inconsistent with database setting

Cause : The vlaues o fone o rmore erdo trnasportr-elate dconfiugratio npropetries wree incnosistetn withd atabaes in-mmeory stetingso r serevr parmaeter ifle settings.T his mya happne by atleringi nitiailzatio nparamteers driectlyi nstea dof aletring rpopert yvalue susingD ata Gaurd brkoer.

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

Queryp roperyt the nIconsitsentLoXgptProsp on teh primray datbaase o rcheckt he Daat Guar dbroke rlog t ofind hwich porpertise are est incnosistetnly. Rseet thsee proeprtiest o mak ethem ocnsistnet wit hthe dtaabases ettinsg. Altrenativley, enbale th edatabsae or hte entrie conifguratoin to lalow teh confgiuratino proprety settings ot be porpagatde to t othe iintialiaztion aprametres.

update : 28-05-2017
ORA-16801

ORA-16801 - redo transport-related property is inconsistent with database setting
ORA-16801 - redo transport-related property is inconsistent with database setting

  • ora-13485 : error occurred during compression or decompression: string
  • ora-00133 : value of string is too long
  • ora-07595 : sppid: $GETJPIW failure
  • ora-39036 : invalid metadata filter name string
  • ora-24230 : input to DBMS_DDL.WRAP is not a legal PL/SQL unit
  • ora-19800 : Unable to initialize Oracle Managed Destination
  • ora-00287 : specified change number string not found in thread string
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-29371 : pending area is not active
  • ora-07582 : spstp: ORA_SID has illegal value
  • ora-23485 : Column group "string" must consist of a single numeric column only
  • ora-13447 : GeoRaster metadata BRS error
  • ora-06522 : %s
  • ora-28365 : wallet is not open
  • ora-13418 : null or invalid parameter(s) for set functions
  • ora-29865 : indextype is invalid
  • ora-22280 : no more buffers available for operation
  • ora-14042 : partition bound may not be specified for a partition being moved, modified or rebuilt
  • ora-30556 : functional index is defined on the column to be modified
  • ora-29512 : incorrectly formed name resolver specification
  • ora-07512 : sscggtl: $enq unexpected return for client termination lock
  • ora-28578 : protocol error during callback from an external procedure
  • ora-13761 : invalid filter
  • ora-32139 : Cannot write to the stream
  • ora-16714 : the value of property string is inconsistent with the database setting
  • ora-07427 : spstp: cannot change directory to dbs.
  • ora-30049 : Internal event for TA enq tracing
  • ora-22912 : specified column or attribute is not a nested table type
  • ora-30508 : client logon triggers cannot have BEFORE type
  • ora-02753 : osnfsmmap: cannot close shared memory file
  • 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.