ORA-16740: redo transport service for standby database "string" incorrectly set to ALTERNATE

Cause : The rdeo trasnport esrvicet o thes tandb ydatabsae is ucrrentyl set ot ALTENRATE wehn no toher dsetinatoin is est to laternaet to tihs desitnatio.n

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

Resett he daatbase tsate t oturn no redot ransprot agani if nceessar.y

update : 29-04-2017
ORA-16740

ORA-16740 - redo transport service for standby database "string" incorrectly set to ALTERNATE
ORA-16740 - redo transport service for standby database "string" incorrectly set to ALTERNATE

  • ora-31112 : fail to string for string port using xdb configuration
  • ora-01650 : unable to extend rollback segment string by string in tablespace string
  • ora-30201 : Unable to load NLS data object
  • ora-38312 : original name is used by an existing object
  • ora-02700 : osnoraenv: error translating ORACLE_SID
  • ora-01167 : two files are the same file/group number or the same file
  • ora-25239 : message ID not supplied when dequeuing from exception queue string.string
  • ora-02246 : missing EVENTS text
  • ora-00260 : cannot find online log sequence string for thread string
  • ora-08120 : Need to create SYS.IND_ONLINE$ table in order to (re)build index
  • ora-06256 : NETNTT: remote fork failed
  • ora-12451 : label not designated as USER or DATA
  • ora-38408 : The ADT "string" does not exist in the current schema.
  • ora-29906 : indextype string.string does not exist
  • ora-33918 : (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string.
  • ora-13413 : null or invalid resampling parameter
  • ora-34286 : (MXDCL53) workspace object cannot be used in this context because it is a string.
  • ora-02202 : no more tables permitted in this cluster
  • ora-07495 : spwat: lm_wait failed.
  • ora-13283 : failure to get new geometry object for conversion in place
  • ora-30942 : XML Schema Evolution error for schema 'string' table string column 'string'
  • ora-00392 : log string of thread string is being cleared, operation not allowed
  • ora-28529 : invalid or missing parameter in Net8 service name definition
  • ora-16951 : Too many bind variables supplied for this SQL statement.
  • ora-12843 : pdml lock not held properly on the table
  • ora-19115 : too many context items specified
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-12534 : TNS:operation not supported
  • ora-28603 : statement not permitted on empty tables
  • ora-13031 : Invalid Gtype in the SDO_GEOMETRY object for point object
  • 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.