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-07-2017

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

  • ora-33448 : (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled.
  • ora-16406 : Primary and standby database software version mismatch
  • ora-27250 : OS system call failure
  • ora-23440 : incorrect public template value
  • ora-02787 : Unable to allocate memory for segment list
  • ora-01140 : cannot end online backup - all files are offline or readonly
  • ora-02178 : correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
  • ora-27546 : Oracle compiled against IPC interface version string.string found version string.string
  • ora-19735 : wrong creation SCN - control file expects initial plugged-in datafile
  • ora-00334 : archived log: 'string'
  • ora-19769 : missing FILE keyword
  • ora-12636 : Packet send failed
  • ora-16034 : FROM parameter is incompatible with MANAGED recovery
  • ora-13465 : null or invalid table or column specification
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-01347 : Supplemental log data no longer found
  • ora-23504 : columns added to table do not match list of columns to be added
  • ora-15153 : cluster not in rolling upgrade
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-03001 : unimplemented feature
  • ora-06321 : IPA: Cannot reach the remote side
  • ora-19637 : backupPieceCreate requires file name when using DISK device
  • ora-29387 : no top-plans found in the pending area
  • ora-07757 : slemcc: invalid handle
  • ora-04010 : the number of values to CACHE must be greater than 1
  • ora-01923 : CASCADE aborted, objects locked by another user
  • ora-37120 : MDX string is null
  • ora-29872 : parameters clause cannot be combined with the specified options
  • ora-24434 : OCIStmtRelease called before OCIStmtPrepare2.
  • ora-00400 : invalid release value string for parameter 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.