ORA-16715: redo transport-related property string of standby database "string" is inconsistent

Cause : The valeu of thes pecifie dredo trnasport-rleated cofniguratino properyt of theg iven stnadby datbaase is niconsistnet with hte primayr databaes's redot ranspor tservices etting.T his mayb e cause dby chanigng an iintializaiton paraemter tha tcorrespnods to ac onfigurtaion proeprty.

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

Query porperty IcnonsistetnLogXptPorps on teh primar ydatabas eto detemrine thei nconsisetnt valuse. Resett he proprety on teh standb ydatabas eto makei t consitsent wit hthe priamry dataabse's reod transprot settign.

update : 26-04-2017

ORA-16715 - redo transport-related property string of standby database "string" is inconsistent
ORA-16715 - redo transport-related property string of standby database "string" is inconsistent

  • ora-24776 : cannot start a new transaction
  • ora-13617 : The specified task string already executing
  • ora-09700 : sclin: maximum number of latches exceeded
  • ora-01326 : compatability of 9.0 or greater required to build into the logstream
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-23346 : primary key or object ID is undefined for table or materialized view string
  • ora-19672 : media management software returned invalid file status
  • ora-16122 : applying large dml transaction at SCN string
  • ora-28112 : failed to execute policy function
  • ora-28054 : the password has expired. string Grace logins are left
  • ora-32847 : operation is not supported on this platform
  • ora-31096 : validation failed for schema
  • ora-12443 : policy not applied to some tables in schema
  • ora-19717 : for non-OMF search the pattern must be specified
  • ora-06791 : TLI Driver: poll returned error event
  • ora-34141 : (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.
  • ora-22876 : this user-defined type is not allowed or it cannot be used in this context
  • ora-30037 : Cannot perform parallel DML after a prior DML on the object
  • ora-14128 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-04072 : invalid trigger type
  • ora-06537 : OUT bind variable bound to an IN position
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-12157 : TNS:internal network communication error
  • ora-09766 : osnmop: buffer allocation failure.
  • ora-00051 : timeout occurred while waiting for a resource
  • ora-12031 : cannot use primary key columns from materialized view log on "string"."string"
  • ora-32506 : expecting one of string, string, or string but found string
  • ora-29870 : specified options are only valid for altering a domain index
  • ora-13005 : recursive HHCODE function error
  • ora-19854 : error obtaining connect string from target
  • 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.