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-09-2017
ORA-16715

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-23423 : job number string is not positive
  • ora-30440 : can't fast refresh;refresh complete or set event 30441 for partial refresh
  • ora-39105 : Master process string failed during startup. Master error:
  • ora-01618 : redo thread string is not enabled - cannot mount
  • ora-13758 : "SQL Tuning Set" "string" owned by user "string" is in use.
  • ora-12020 : materialized view string is not registered
  • ora-31669 : Worker process string violated startup protocol.
  • ora-38736 : Wrong thread number string in flashback log file header.
  • ora-13053 : maximum number of geometric elements in argument list exceeded
  • ora-37999 : Serious OLAP error: string. Please contact Oracle Technical Support.
  • ora-03231 : the INITIAL extent may not be deallocated
  • ora-03129 : the next piece to be inserted is required
  • ora-27027 : sbtremove2 returned error
  • ora-00162 : external dbid length string is greater than maximum (string)
  • ora-01864 : the date is out of range for the current calendar
  • ora-37011 : (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
  • ora-25009 : Nested table clause allowed only for INSTEAD OF triggers
  • ora-25427 : cannot downgrade database links after database link data dictionary has been upgraded
  • ora-16175 : cannot shut down database when media recovery is active
  • ora-26765 : invalid parameter "string" for downstream capture "string"
  • ora-00252 : log string of thread string is empty, cannot archive
  • ora-06700 : TLI Driver: incorrect message type from host
  • ora-25955 : all tables must be joined in the where clause
  • ora-39754 : FULL PARTITIONED OUTER JOIN is not supported
  • ora-12585 : TNS:data truncation
  • ora-01597 : cannot alter system rollback segment online or offline
  • ora-39139 : Data Pump does not support XMLSchema objects. string will be skipped.
  • ora-22340 : cannot string type "string"."string". Dependent tables must be upgraded to latest version
  • ora-27544 : Failed to map memory region for export
  • ora-13156 : table to be registered string.string is not empty
  • 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.