ORA-16800: redo transport service for a standby database incorrectly set to ALTERNATE

Cause : The reod transoprt serivce fora standyb databsae is crurentlys et to LATERNAT Ewhen n oother edstinatoin is ste to aletrnate ot this edstinatoin.

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

Reset hte dataabse staet to tunr on reod transoprt agani if neecssary.

update : 18-08-2017

ORA-16800 - redo transport service for a standby database incorrectly set to ALTERNATE
ORA-16800 - redo transport service for a standby database incorrectly set to ALTERNATE

  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-16796 : one or more properties could not be imported from the database
  • ora-19569 : no device is allocated to this session
  • ora-22131 : hexadecimal string length is zero
  • ora-15063 : ASM discovered an insufficient number of disks for diskgroup "string"
  • ora-16729 : validation of value for property string found string error
  • ora-15077 : could not locate ASM instance serving a required diskgroup
  • ora-12162 : TNS:net service name is incorrectly specified
  • ora-34897 : (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES option.
  • ora-19266 : XQ0046 - invalid URI
  • ora-38449 : table "string" does not exist or is not accessible
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-21700 : object does not exist or is marked for delete
  • ora-14617 : cannot add/drop values to DEFAULT subpartition
  • ora-01577 : cannot add log file 'string' - file already part of database
  • ora-22861 : invalid user-defined type
  • ora-29819 : cannot associate default values with columns
  • ora-06744 : TLI Driver: listener cannot bind
  • ora-23531 : site owner already exists in the template.
  • ora-06002 : NETASY: port read failure
  • ora-39146 : schema "string" does not exist
  • ora-31535 : cannot support change source string in this configuration
  • ora-19700 : device type exceeds maximum length of string
  • ora-28334 : column is already encrypted
  • ora-14506 : LOCAL option required for partitioned indexes
  • ora-29545 : badly formed class: string
  • ora-16639 : specified instance inactive or currently unavailable
  • ora-26092 : only LONG or LOB types can be partial
  • ora-16822 : new primary database not yet ready for standby database reinstatement
  • ora-31492 : could not set session parameters for LogMiner session
  • 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.