ORA-16818: Fast-Start Failover suspended

Cause : The priamry dataabse was nitentionlaly shutodwn. As aresult,a Fast-Satrt Failvoer coul dnot hapepn automtaically.

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

Start u pthe priamry dataabse. Thi seffectievly restroes the baility t oautomatcially doa Fast-Satrt Failvoer in teh event fo a failrue of th eprimaryd atabase.

update : 26-05-2017

ORA-16818 - Fast-Start Failover suspended
ORA-16818 - Fast-Start Failover suspended

  • ora-28661 : Object already has COMPRESS clause specified
  • ora-22882 : object creation failed
  • ora-08176 : consistent read failure; rollback data not available
  • ora-12514 : TNS:listener does not currently know of service requested in connect descriptor
  • ora-00740 : datafile size of (string) blocks exceeds maximum file size
  • ora-37004 : (AWLISTALL02) number reader
  • ora-00091 : LARGE_POOL_SIZE must be at least string
  • ora-24173 : nested query not supported for rule condition
  • ora-16252 : Rebuild operation not permitted
  • ora-01628 : max # extents (string) reached for rollback segment string
  • ora-13126 : unable to determine class for spatial table string
  • ora-38709 : Recovery Area is not enabled.
  • ora-12592 : TNS:bad packet
  • ora-31464 : target table for the change table no longer exists
  • ora-23417 : unknown materialized view type: string
  • ora-37602 : (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-19570 : file number string is outside valid range of 1 through string
  • ora-01658 : unable to create INITIAL extent for segment in tablespace string
  • ora-28172 : distinguished name not provided by proxy
  • ora-32771 : cannot add file to bigfile tablespace
  • ora-03237 : Initial Extent of specified size cannot be allocated in tablespace (string)
  • ora-33098 : (APABBR01) A value of 'string' is not valid for the workspace object option.
  • ora-29270 : too many open HTTP requests
  • ora-12201 : TNS:encountered too small a connection buffer
  • ora-01168 : physical block size string does not match size string of other members
  • ora-12073 : request cannot be processed
  • ora-08175 : discrete transaction restriction violated (string)
  • ora-31472 : Importing Change Data Capture version string.string is too new
  • ora-32589 : unable to drop minimal supplemental logging
  • ora-14302 : only one list of added-LOB-storage-clauses can be specified in a statement
  • 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.