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 : 22-09-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-14267 : cannot specify PARALLEL clause when adding a (Composite) Range partition
  • ora-16098 : inaccessible standby database forced shutdown to protect primary
  • ora-36873 : (XSTFDSC03) Column type must be specified explicitly.
  • ora-01551 : extended rollback segment, pinned blocks released
  • ora-25191 : cannot reference overflow table of an index-organized table
  • ora-39207 : Value string is invalid for parameter string.
  • ora-19043 : Multiply nested XMLROOT function disallowed
  • ora-16047 : DGID mismatch between destination setting and standby
  • ora-24157 : duplicate variable name string
  • ora-21615 : an OTS (named or simple) instance failed
  • ora-16563 : unable to add value, syntax error at "string"
  • ora-01868 : the leading precision of the interval is too small
  • ora-07635 : smsdbp: $SETPRT failure
  • ora-13514 : Metric Capture too close to last capture, group string
  • ora-12826 : hung parallel query server was killed
  • ora-22808 : REF dereferencing not allowed
  • ora-28172 : distinguished name not provided by proxy
  • ora-29903 : error in executing ODCIIndexFetch() routine
  • ora-30131 : number of keys being set exceeds allocation
  • ora-31442 : operation timed out while acquiring lock on string
  • ora-30568 : cannot drop log group - nonexistent log group
  • ora-30395 : dimension options require the COMPATIBLE parameter to be string or greater
  • ora-30081 : invalid data type for datetime/interval arithmetic
  • ora-27074 : unable to determine limit for open files
  • ora-28335 : referenced or referencing FK constraint column cannot be encrypted
  • ora-06044 : NETDNT: connect failed, byte count quota exceeded
  • ora-02331 : cannot create constraint on column of datatype string
  • ora-39768 : only one direct path context top level column array is allowed
  • ora-16217 : prepare to switchover has not completed
  • ora-38726 : Flashback database logging is not 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.