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 : 22-07-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-28611 : bitmap index is corrupted - see trace file for diagnostics
  • ora-31492 : could not set session parameters for LogMiner session
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-24907 : invalid pair of callback and recepient protocol attributes
  • ora-16705 : internal error in resource guard
  • ora-06447 : ssvpstp: Incorrect parameter passed to function call
  • ora-00723 : Initialization parameter COMPATIBLE must be explicitly set
  • ora-12096 : error in materialized view log on "string"."string"
  • ora-19706 : invalid SCN
  • ora-14505 : LOCAL option valid only for partitioned indexes
  • ora-01107 : database must be mounted for media recovery
  • ora-02222 : invalid PCTINCREASE storage option value
  • ora-06600 : LU6.2 Driver: SNA software is not loaded
  • ora-30459 : 'string.string' cannot be refreshed because the refresh method is NONE
  • ora-30991 : cannot use DOM to add special attribute to schema-based parent
  • ora-23453 : requested operation is not supported on top flavor
  • ora-28268 : Exceeded the maximum allowed size for Context information in a session
  • ora-12560 : TNS:protocol adapter error
  • ora-24404 : connection pool does not exist
  • ora-09828 : SCLFR: atomic latch return error.
  • ora-22619 : all collection elements have already been accessed
  • ora-01070 : Using an old version of Oracle for the server
  • ora-32305 : RepAPI materialized views with user-defined types are not supported
  • ora-29848 : error occurred in the execution of ODCIINDEXMERGEPARTITION routine
  • ora-31088 : object "string"."string" depends on the schema
  • ora-32337 : cannot alter materialized view with pending changes refresh on commit
  • ora-31486 : cannot support column string in this configuration
  • ora-31183 : Node type string cannot be converted to desired type
  • ora-32134 : Cannot assign LOBs
  • ora-16075 : standby database destination mismatch
  • 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.