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 : 30-04-2017
ORA-16800

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-12912 : Dictionary managed tablespace specified as temporary tablespace
  • ora-16237 : SGA specified for Logical Standby is too small
  • ora-26085 : direct path operation must start its own transaction
  • ora-01918 : user 'string' does not exist
  • ora-25445 : invalid column number: string for table alias: string
  • ora-12068 : updatable mview log for mview "string"."string" does not exist
  • ora-08309 : sllfop: Cannot fstat file
  • ora-02213 : duplicate PCTUSED option specification
  • ora-33004 : (XSAGDNGL01) workspace object is not a relationship array.
  • ora-16709 : standby archived log location settings conflict with flash recovery area
  • ora-22297 : warning: Open LOBs exist at transaction commit time
  • ora-13008 : the specified date format has an invalid component
  • ora-22973 : size of object identifier exceeds maximum size allowed
  • ora-01536 : space quota exceeded for tablespace 'string'
  • ora-38907 : DML error logging is not supported for FILE column "string"
  • ora-06793 : TLI Driver: server cannot create new process
  • ora-16569 : Data Guard configuration is not enabled
  • ora-01617 : cannot mount: string is not a valid thread number
  • ora-13768 : Snapshot ID must be between string and string.
  • ora-38472 : VARCHAR representation of the data item is too long.
  • ora-12696 : Double Encryption Turned On, login disallowed
  • ora-40109 : inconsistent logical data record
  • ora-36982 : (XSRELGID03) The grouping variable/relation workspace object must be dimensioned by all dimensions of the source relation workspace object that have more than one value in status.
  • ora-40103 : invalid case-id column: string
  • ora-13615 : The task or object string is greater than the maximum allowable length of 30 characters.
  • ora-02795 : Request list is empty
  • ora-24085 : operation failed, queue string is invalid
  • ora-10704 : Print out information about what enqueues are being obtained
  • ora-12987 : cannot combine drop column with other operations
  • ora-19116 : too many xmlspace declarations
  • 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.